Didn't receive the attached file

[crismartins]

Hello,

A person sent an email with a RTF file attached. The recipient receives an email with nothing in body and with a message.txt attached. Where is the RTF file?

The message.txt looks like this:

Received: from [10.1.20.28] (TCPBASAH1 [173.97.1.200]) by
graviola.server.basa with SMTP (Microsoft Exchange Internet Mail Service
Version 5.5.2655.55)
id L7AB8A9H; Fri, 13 Jun 2003 10:44:20 -0300
MIME-VERSION: 1.0
X-MAILER: MCP/AS EMAIL (49.189.018) 05/01/2003
X-ORIGINATING-IP: [173.97.1.200]
DATE: FRI, 13 JUN 2003 10:46:42 -0300
FROM: USO DA OPERACAO <DIVOP@TESTE.TESTE>
SUBJECT: TESTE EXTRATO
TO: CRISGMARTINS@YAHOO.COM.BR
CONTENT-TYPE: MULTIPART/MIXED; BOUNDARY=BOUNDARY42
THIS IS THE PREAMBLE AREA OF A MULTIPART MESSAGE. MAIL READERS THAT
UNDERSTAND MULTIPART FORMAT SHOULD IGNORE THIS PREAMBLE.

IF YOU ARE READING THIS TEXT, YOU MIGHT WANT TO CONSIDER CHANGING TO A MAIL
READER THAT UNDERSTANDS HOW TO PROPERLY DISPLAY MULTIPART MESSAGES.
--BOUNDARY42
CONTENT-TYPE: TEXT/ENRICHED

TESTE
--BOUNDARY42
CONTENT-TYPE: APPLICATION/X-data
CONTENT-TRANSFER-ENCODING: BASE64
CONTENT-DISPOSITION: ATTACHMENT; FILENAME=extrato2

e1xydGYxXG.......

ICAgIERBVEE...==
--BOUNDARY42

Any ideas are wellcome!

Thanks a lot
Cristiana

 

[rubbaninja]

From exchange doc.

Specifying the Default Attachment Content Format

Use the Internet Mail property page to specify whether outbound messages with attachments will be encoded using Multipurpose Internet Mail Extensions (MIME) or uuencode. This option can be specified by e-mail domain. These settings override the default format.

Settings configured in client applications can override the default setting and the settings specified by e-mail domain. If the client specifies no content format option and no match is found in the e-mail domain options, the default setting will be used.


Note Message content should be set for UUENCODE when transferring messages to Microsoft Mail 3.x with Microsoft Mail Gateway to SMTP.


Select the Internet Mail tab.
Under Attachments (Outbound), select MIME or UUENCODE.
Choosing MIME means that all attachments will be encoded using MIME, except when the client software overrides the option. If a MIME message is delivered to a non-MIME-aware client, the attachment may not be usable.
Option Description
Plain text A plain text MIME body part is generated for the message. If HTML is also selected, Microsoft Exchange Server provides both Hypertext Markup Language (HTML) and plain text in a MIME multipart/alternative message.
HTML A MIME body part in HTML is generated for the message. If Plain text is also selected, Microsoft Exchange Server provides both HTML and plain text in a MIME multipart/alternative message. HTML is an Internet standard that enables rich-text formatting such as bold, color, and italic to appear in messages.
Binhex Renders the message body as text with any attachments encoded by the BinHex method, which is commonly used in the Macintosh operating system to encode 8-bit data transmitted on the Internet.


For more information about MIME and uuencode, see Microsoft Exchange Server Concepts and Planning. For more information about e-mail domain options, see &quot;Specifying Message Content by E-mail Domain&quot; later in this chapter.

 

[chirito]

I am having the same problem that you are, however, I am the sender in this case. So, I really have no access to the exchange server and I don't know exactly what needs to be done for them to be able to see the attachment correctly. I understand that the users are using the Base64 enconding setting. Any help would be greatly appreciate it.
Thanks,
Jose