Problem:

With WinSpool/400 Email Report Server, you get the error:
 
SMTP: Inbound Attachment Named PART.00x
 

Solution:

Note: This solution is adapted from a Novell knowledge-base document.
 
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. There are instructions within each part 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, and so on.
 
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.

    To solve this problem, apply SMTP3.EXE (TID2929548) to correct some of these unknown MIME parts. Other unknown MIME parts have to be determined on a case-by-case basis.

  2. The message is sent from Microsoft Exchange in Microsoft Exchange Rich Text Format. This is not supported by the GroupWise Gateway.

    To turn off the Microsoft Exchange Rich Text Format feature in Microsoft Exchange:

    1. In Microsoft Exchange, click Tools > Address Book
    2. Right-click the recipient's address and click Properties.
    3. Disable Always send messages in Microsoft Exchange rich text format.
  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.

    Contact the firewall vendor to address this problem.

  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]

    A request to have SMTP recognize attachment names from the Content-Type's name field has been reported to Novell development.


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: December 10, 2016