Believe the key indication is the ms-tnef - on the 5.5 IMS there is a setting on the Internet Mail tab, Advanced options called "Send Microsoft Exchange rich text formatting" - options are User, Always & Never. Believe this can also be set on a per domain basis. Having this set to always or user and having the user set the equivalent option can cause exactly this result when sending to some non-MS mail systems. As I recall, tnef (Transport Neutral Encoding Format?) is intended for sending from MS to MS across non-MS relays - not all non-ms systems understand this format.
"Crosby, Tim (Sarcom)" wrote: > Oh, and by the way, I just looked at one of the replies back from someone > who couldn't open the attachment. This appears where the attachment would > normally be: > > > > > ------------------------------------------------------------------------ > > > > > > Part 1.2 Type: application/ms-tnef > > > Encoding: base64 > > > > ------------------------------------------------------------------------ > > Name: Club Pub Services.doc > > Club Pub Services.doc Type: Winword File (application/msword) > > Encoding: base64 > > -----Original Message----- > From: Crosby, Tim (Sarcom) [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 16, 2002 11:22 AM > To: MS-Exchange Admin Issues > Subject: Problems with Distribution list > > Got a strange one that I'm hoping someone has the solution for. One of our > users regularly sends out attachments to a bunch of external email address > that are not setup as custom recipients on our system. She has a personal > distribution list that she uses which contains all the addresses. Some of > the people that she sends to report that the attachment arrives at their end > with an attachment named "C.DTF" instead of the file she attached. > > Q259065 says this can happen when sending Rich Text messages to a Lotus > Notes MTA. But I checked the last time she sent a message and verified that > it was all in plain text. She still says some people reported getting the > C.DTF file. But it only seems to happen when sending to the group as a > whole. When people send her replies saying they couldn't open the file, she > then replies directly to that person with the original attachment, and they > always receive that one fine. From looking at the DL, it looks to have > about 65 addresses in it. > > Anyone seen this one before? Should I try putting those names in our system > as custom recipients? Or maybe creating a DL on the exchange server with > all those names in it? > > By the way, Exchange 5.5, SP4 running on W2K server, SP2. Client is Outlook > 2000. > > List Charter and FAQ at: > http://www.sunbelt-software.com/exchange_list_charter.htm > > List Charter and FAQ at: > http://www.sunbelt-software.com/exchange_list_charter.htm "WorldSecure Server <safeway.com>" made the following annotations on 01/16/02 14:41:13 ------------------------------------------------------------------------------ Warning: All e-mail sent to this address will be received by the Safeway corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain information proprietary to Safeway and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. ============================================================================== List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
