Product Area:  Technical Area: Platform: Cross Platform
SPR# TMIZ5P3EY3 - The itemizer functionality ( how we process parts of a message ) has never correctly handled messages with missing or out-of-order boundaries. According to the rfcs, if an application finds a boundary from an ancestor mime entity (i.e., a boundary defined at an outer nesting level), then it should 'wrap up' the processing of the current enity and continue processing at the indicated Router level.
The itemizer now handles this situation correctly, processing the rest of the message, rather than rolling the entire messsage stream into a $RFC822.eml attachment.
APAR: LO05553
What is an APAR?
Last Modified on 12/10/2013 |  |
|
|
|
|
|