SMTP: Inbound Attachment Named PART.00x
From Support
| If you have a question or seek clarification, please call Technical Support. |
Problem:
SMTP: Inbound Attachment Named PART.00x
Solution:
Novell Knowledgebase Document
SMTP: Inbound Attachment Named PART.00x (Last modified: 18MAY1999) This document (2914527) is provided subject to the disclaimer at the end of this document.
Forward this document to a colleague Provide feedback about this document to Novell
Symptom Certain messages received from the Internet have attachment names of PART.001, PART.002, etc.
Troubleshooting additional keywords: part000, part001, part00x, part00?, part.000, part.00?, exchange, RTF, part.00x
Cause An attachment with a name PART.001 means the SMTP/MIME gateway did not understand part of the MIME message. MIME messages are split into parts using a boundary definition to separate each of the parts. Within each part are instructions to identify the type of part being read. If the gateway does not understand a part of the message, the unknown part will be clipped out of the message and attached as an attachment with the generic name PART.001. Each additional unknown part will be given the incremented name PART.001, PART.002, PART.003, etc. There could be several reasons why a message part is unknown: 1. The content-type is multipart/appledouble. Until SMTP2.EXE (gateway code prior to 4/18/97), this was an unsupported content type. 2. The message is sent from Microsoft Exchange in "Microsoft Exchange Rich Text Format." This is not supported by the GroupWise Gateway. 3. The CheckPoint FireWall-1 inserts a blank line within an UUENCODED attachment. This bug in the firewall software causes the gateway's UUDECODE to fail. 4. The attachment header is missing the Content-Disposition line. The Content-Disposition line followed by a blank line should immediately precede the attachment:
=_NextPart_IEX_352a823c3d822.891978300
Content-Type: application/msword; name="attach.doc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="attach.doc"
0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAIQAAAAAAAAAA [snip]
Solutions Depending on the cause of the problem, choose the appropriate solution below: 1. Apply SMTP3.EXE (TID2929548) to correct some of these unknown MIME parts. Other unknown MIME parts will have to be determined on a case-by-case basis. 2. According to Microsoft, to turn off the Microsoft Exchange Rich Text Format "feature" in Exchange,
A. In Microsoft Exchange, click Address Book on the Tools menu. B. Right-click the recipient's address. C. Click Properties on the menu that appears. D. Disable the "Always send messages in Microsoft Exchange rich text format" option.
3. Contact the firewall vendor to address this problem. 4. A request to have SMTP recognize attachment names from the Content-Type's name field has been reported to Development.
Please select if this document solved your problem.
Document Title: SMTP: Inbound Attachment Named PART.00x Document ID: 2914527 Creation Date: 04OCT1996 Modified Date: 18MAY1999 Document Revision: 16 Novell Product Class: Groupware Novell Product and Version: GroupWise
DISCLAIMER The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
