LO88655: ATTACHMENTS WITH LONG FILENAMES MAY NOT SYNC TO DEVICE
Direct links to fixes
Closed as program error.
Per MIME standards, long parameter values in MIME headers can be broken up into smaller enumerated units to avoid wrapping. For example, the Content-Disposition MIME header could have the following parameters, rather than a single "filename" parameter: filename*0="sampleAttachmentName"; filename*1="ABC.gif"; which is the functional equivalent of: filename="sampleAttachmentNameABC.gif"; Before this fix, if Traveler did not find a "filename" parameter in an attachment's MIME header, in some cases it may have generated an invalid attachment name containing only a file extension, such as ".gif", ".jpg", etc. This can cause unexpected StringIndexOutOfBoundsExceptions when comparing attachment refIds and prevent the attachment from streaming to the device. With this APAR, Traveler will prevent these exceptions and also search for enumerated "filename" and "name" parameters, to account for the cases where longer values have been broken up into multiple parts.
MIME document format standards allow long attachment names to be broken into multiple smaller parameters. This is not very common, but it is acceptable format.
The IBM Traveler server was updated to handle this format correctly when syncing Mime content documents.
This fix is included in IBM Traveler 220.127.116.11 and will be included in all future releases. For the latest available maintenance information see this technote: http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
LOTUS NOTES TRA
Fixed component ID
Applicable component levels