Notes/Domino Fix List
 |  |
| SPR # BACY4MTNWT | Fixed in 5.0.5 release |  |
Product Area: Client Technical Area: Editor - Attachments Platform:
SPR# BACY4MTNWT, LAE4JHCEW, CEA4CEDDG - Added a new user preference: "Show in-line MIME images as attachments," to fix a problem introduced with the 5.0.3 SMTP server, where messages sent with attachments (images) were received in the body of the message. When this setting is checked all multipart/mixed, in-line images are displayed as attachments. The setting corresponds to a NOTES.INI variable called "ShowIMIMEImagesAsAttachments". Administrators can push this NOTES.INI variable to users desktops.
Technote Number: 1084726
Problem:
This issue was reported to Lotus Quality Engineering and has been addressed in
Notes 5.0.5 and Notes 6.
Excerpt from the Lotus Notes and Lotus Domino Release 5.0.5 QMR fix list:
Editor - Attachments
SPR# BACY4MTNWT - Added a new user preference: "Show in-line MIME images as
attachments," to fix a problem introduced with the 5.0.3 SMTP server, where
messages sent with attachments (images) were received in the body of the
message. When this setting is checked all multipart/mixed, in-line images are
displayed as attachments. The setting corresponds to a NOTES.INI variable
called "ShowIMIMEImagesAsAttachments". Administrators can push this NOTES.INI
variable to users desktops. Also provides a fix for CEA4CEDDG.
NOTE: This NOTES.INI parameter only works with images as attachments; text file
attachments are still problematic.
Zipping the attachments (GIF or JPG) is also a viable workaround to this
issue. Zipping the attachments will result in the images being left as is.
Supporting Information:
The message that was received by the Domino (SMTP) server was tagged by the
sending system as being an inline image. The Content-Disposition field
instructs the receiving system how to handle the data that was sent. The
sending system tagged this message as being "inline" and the Domino server
honored the sending system's request.
There is a difference in behavior between the 4.6x SMTP MTA and the R5.x SMTP
task. In using 4.6x with the SMTP MTA, the Content-Disposition field was not
used during conversion of the message. In 4.6x, the conversion process
utilized the Content-Type field. The Content-Type field associates the MIME
subtype (or application used to generate the attachment) followed by a Name=
FilenameOfTheAttachment.
Messages that included the Content-Disposition: Inline tag were not honored and
all attachments were left as attachments. More >
Last Modified on 05/31/2001
Go back
|