Windows Forum

Ask something
Discussion Locked

Email messages contain message.txt

0 helpful
5 replies

by srbrandt

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Message that is received by user:Microsoft Exchange Server received an Internet message that could not be processed and it has a message.txt included.

They receive Adobe Illustrator attachments from a customer and they get this message everytime.

This is the part of the message.txt that Exchange appears not to understand with a little of the random characters attached:

(See attached file: 01100509 (Tesoro HS))(See attached file: 01100298
(Coshocton))(See attached file: 01100006 (La Center))(See attached file:
01100005 (La Center))

----PTCP_00000819030bf007d1--

--0__=85256AEF006FBE318f9e8a93df938690918c85256AEF006FBE31
Content-type: application/applefile;name="01100509 (Tesoro HS)"; x-mac-type="45505346"; x-mac-creator="41525435"
Content-transfer-encoding: base64

AAUWBwACAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAADAAAASgAAABQAAAAIAAAAXgAAABAAAAAJAAAA
bgAAACAAAAACAAAAjgABvEQwMTEwMDUwOSAoVGVzb3JvIEhTKQNpld8DaZXhAAAAAAAAAABFUFNG

Any ideas would be appreciated,

Thank you,
Scott

5 replies

by glenfahan

It looks like a mac font issue. If you are currently opening the file on a PC, try a mac. We occasionaly have similar issues with customers. Sorry I only have a work around and not a fix. Except to have the customer limit which fonts they use.

by stillatit

What is happening is that for some reason your Exchange server is not liking the attachment. Offhand, the "Content-type: application/applefile;" is probably the problem.

Binary attachments are typically encoded in various ways so that only printable characters are included in the mail. In your example, "Content-transfer-encoding: base64" defines how the data is translated to printable characters, and how they should be translated back. The translated data is the junk starting "AAUWBwACAAAAAAAAAAAA" in your example.

A secondary problem is that Mac files often have two pieces, known as the resource fork and the data fork. PC's do NOT know how to deal with this at all. Your server may be choking on this.

There is a known bug in Exchange, and a fix from Microsoft. The article title is: XFOR: Macintosh Attachments Over IMC Are Named Message.txt. See the following url (delete any spaces or line breaks)

http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q164859

Another possible fix: Try packing the files using Stuffit on the Mac. You can create .sit files. Alternately, create .zip files. Attach those files rather than the original application files.

Good luck.

by shanghai sam

This pointed me in the right direction. They switched clients from Outlook Express to Notes.

Thank you
Scott

This discussion is closed to new replies.