Technote Number: 1098239
Problem:
This issue was reported to Lotus Quality Engineering and has been addressed in
Domino 5.0.6.
Excerpt from the Lotus Notes and Lotus Domino Release 5.0.6 QMR fix list:
SPR# BACY4HMJSN - Fixed a problem, which occurred at the first delivery hop,
when decoding uuencoded attachments in non-mime messages that contain
content-transfer-encoding information.
Supporting Information:
As part of troubleshooting this issue, the message data was trapped inbound on
the R5 SMTP server, as outlined in the document titled "How to Trap Inbound
SMTP Messages on a Domino 5.x Server" (#178652 ). It was found that the data
within the .TMP file contained an additional field, not relevant to a UUencoded
message. This "Content-Transfer-Encoding" field had been added to each of the
suspect messages from the sending system, and the presence of this field on a
non-MIME message resulted in the Domino server incorrectly converting it.
It is unknown which system added this field to the document. The
Content-Transfer-Encoding line was present on the message, prior to routing
inbound to Domino. Editing the .TMP file that was provided and removing the
field Content-Transfer-Encoding=7Bit field allowed the message to be converted
successfully on the Domino server.
Related Documents:
How to Trap Inbound SMTP Messages on a Domino 5.x Server
Document #: 178652 More >
|  |
|
|
|
|
|