Google
Search WWW Search msexchangetips.blogspot.com

Wednesday, August 23, 2006

Exchange: Attachments Gets Converted to ATT###.txt

Summary:

A user in your organization reports that attachments sent to him from an external party, is coming in as ATT###.txt


Cause:

In this scenario, a user called in stating that an attachment that was sent from an external party Excite.com is coming in as ATT###.txt. What we found out in this scenario is that the external contact was not composing a new message in Excite, but he was actually fowarding a message that he received in his Excite account to our internal user. When the external user composed a new message from his Excite account with an attachment, the internal user was able to receive the message. However, if the Excite user was to foward a message with an attachment to our internal user it would come in the format as ATT###.txt.


The way an existing mail with attachment is encoded by the messaging Server at Excite, causes the attachment to lose format. This may be caused by several other domains other than Excite.


James Chong
MCSE M+, S+, MCTS, Security+
msexchangetips.blogspot.com


How useful was this article? Want to see a tip not listed? Please leave a comment.

8 Comments:

Anonymous Anonymous said...

Precisely what attachment encoding caused this problem? From what I've seen, the "several other domains" constitute the vast majority of the Internet. Is there any reason to believe this is not an Exchange bug concerning the MIME de/encoding? I'm trying to track down some specific examples. One example I do have, transmitted from Exchange by SMTP to a Postfix MTA, has the actual email text containing neither the correct attachment nor any MIME part labeled "ATT...txt". MS Outlook may be trying to patch up broken MIME encoding and generating the bogus ATT file attachment.

8:55 AM  
Anonymous Anonymous said...

Precisely what attachment encoding caused this problem? From what I've seen, the "several other domains" constitute the vast majority of the Internet. Is there any reason to believe this is not an Exchange bug concerning the MIME de/encoding? I'm trying to track down some specific examples. One example I do have, transmitted from Exchange by SMTP to a Postfix MTA, has the actual email text containing neither the correct attachment nor any MIME part labeled "ATT...txt". MS Outlook may be trying to patch up broken MIME encoding and generating the bogus ATT file attachment.

8:56 AM  
Anonymous Anonymous said...

Is there any solution to fix this problem or need to know what should be done to fix this problem

9:20 PM  
Anonymous Anonymous said...

I've seen this happen sometimes when using systems that set the Content-Class header to Content-class.
Try checking that and see if the problem goes away.

If it does, fix the sending application to use the proper Content-Class header

5:35 PM  
Anonymous Anonymous said...

God. I truly hate exchange. This has been goingon or a LONG time and there is no fix that works.

9:15 AM  
Anonymous Anonymous said...

I see this happening when emails are sent out from Horde Webmail. The receiving user's Outlook is renaming the attachment to ATTxxxxx.xxx. I found information about something that the file name is using Multibyte Characters (that isn't supported by Outlook). This is happening to only one attachment when multiple attachments are included. File opens fine, it is just renamed. Any solutions?

4:08 PM  
Blogger longge said...

replica handbags began designing luggage for the wealthy that traveled. His first invention was to design lv that was flat and therefore easy to stack in railway carriages. It gained popularity at lightening speed. It didn't take long before his competition was copying his design. In 1854 the replica louis vuitton business came to be, as luggage began to be replaced with replica bags ideas for handbags.

6:39 PM  
Anonymous Anonymous said...

A clients sends us a file that contains 3 attachments, all encrypted using pgp.
The names are significant and should tell us how to handle the files - its all in the name.

We see the messages as ATT....att

Email sent by MS Outlook 2010 via Exchange Server, and popped by ColdFusion using CFPOP.

Which piece of this puzzle is misinterpreting the attachment file names ?

Cheers

4:24 PM  

Post a Comment

<< Home

xml:lang="en" lang="en"> MS Exchange Tips: Exchange: Attachments Gets Converted to ATT###.txt