Well then if everyone is on the GAL and the DL is on the GAL, first thing I
would do is ensure none of them have each others names in their Persona
Contacts or Personal Address book. If "J Smith the boss" is on both, even on
a GAL DL, the personal settings would take precedence (rule this out from
the get go).

-----Original Message-----
From: Carmila Fresco [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 10, 2003 12:19
To: Exchange Discussions
Subject: RE: Message Format


It's about 2 users sending to a distribution list.  The users say they
picked the DL from the GAL.  They're sending the message with attachments
and are using rich-text format. 

I know it's only 2 users but they're sending the email messages to the big
bosses and it's been driving us nuts.  


-----Original Message-----
From: Finch Brett [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 10, 2003 11:05 AM
To: Exchange Discussions

 I haven't seen all the tracks to this but is it just a couple users to a
couple users or an entire site to site with this 'dat' problem? If it's just
a couple users I would ensure their personal contact list doesn't have
anything special set and they are using that instead of the GAL. From site
to site the3 format depends on the version of Exchange I believe, in 5.5
it's x400, not sure if everything is SMTP or not in 2000.

-----Original Message-----
From: Carmila Fresco [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2003 11:26
To: Exchange Discussions
Subject: Message Format



When sending a message between exchange servers in the org, does exchange
follow the internet message formats?  Or is the message format only followed
then you actually send an email message outside of your org?

I'm still stuck with my winmail.dat problem between exchange servers. 

Thanks,
Carmila




This email message may contain information that is confidential and
proprietary to Babcock & Brown or a third party.  If you are not the
intended recipient, please contact the sender and destroy the original and
any copies of the original message.  Babcock & Brown takes measures to
protect the content of its communications.  However, Babcock & Brown cannot
guarantee that email messages will not be intercepted by third parties or
that email messages will be free of errors or viruses.


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&;
lang
=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&;
lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]






This email message may contain information that is confidential and
proprietary to Babcock & Brown or a third party.  If you are not the
intended recipient, please contact the sender and destroy the original and
any copies of the original message.  Babcock & Brown takes measures to
protect the content of its communications.  However, Babcock & Brown cannot
guarantee that email messages will not be intercepted by third parties or
that email messages will be free of errors or viruses.


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang
=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: 
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to