Technote Number: 1109097
Problem:
This issue was reported to Quality Engineering as SPR# PPET5M2MBS and has been
fixed in Domino 6.5.4 and 7.0.
Excerpt from the Lotus Notes and Domino Release 6.0.5 / 6.5.4 MR fix list
(available at http://www.ibm.com/developerworks/lotus):
MIME
SPR# PPET5M2MBS - This fixes the problem where message with attachments from
non-Notes senders over the Internet were not correctly decoded attachments and
could not be viewed/opened.
Refer to the Upgrade Central site for details on upgrading Notes/Domino.
Workaround
To avoid the issue, either the MIME message creator must use multipart/mixed,
or the Notes recipient's Person document must be set to a mail storage
preference of Notes Rich Text. The Domino Router renders the unreferenced
attachment as though it is an independent file in the MIME stream (i.e., as if
the content type were multipart/mixed.)
The issue is due to the way in which the MIME stream was sent by the
originating client. The message was sent as "Content-Type: multipart/related"
but did not properly reference this attachment within the MIME body part.
Copying the message with a Notes 6.x client into a local copy of a mail file
based on a 6.x design may result in the attachment becoming accessible. It was
noted that messages exhibiting this behavior will have the entry " Host: 2304"
in the $FILE field. This copying modifies the "Host" entry in the $FILE field
to "Host: UNKNOWN". Once this modification occurs, the message can be copied
back to its source mail file, and the document will be visible.
Supporting Information:
RFC 2387 describes the use of "Content-Type: multipart/related". It is to be
used when several components are integral parts of the same message and are to
be used together; for example, a .gif or .jpg file to be rendered within a
frame or section in the body of a message. When the R5 or Notes 6.x client
renders a MIME message with this content type, and (1) an attachment is not
referenced as being an integral part or component of the message and (2) is
instead an independent file in the MIME stream--yet within the main boundaries
of the stream content type, the attachment is not rendered and made accessible
to the addressee.
A sample header is included below:
Content-Type: multipart/related; boundary=13862295.1047036818632.123465789 More >
|  |
|
|
|
|
|