[
https://issues.apache.org/jira/browse/MIME4J-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613578#action_12613578
]
Oleg Kalnichevski commented on MIME4J-56:
-----------------------------------------
I did attach a patch, didn't I?
https://issues.apache.org/jira/secure/attachment/12386044/mime4j.patch
The patch is against the streams-refactoring branch.
Oleg
> In nested multiparts outer boundaries are not recognized when parsing inner
> multiparts
> --------------------------------------------------------------------------------------
>
> Key: MIME4J-56
> URL: https://issues.apache.org/jira/browse/MIME4J-56
> Project: Mime4j
> Issue Type: Bug
> Affects Versions: 0.4
> Reporter: Stefano Bagnara
> Assignee: Stefano Bagnara
> Fix For: 0.4
>
> Attachments: mime4j.patch
>
>
> 5.1.2. Handling Nested Messages and Multiparts
> The "message/rfc822" subtype defined in a subsequent section of this
> document has no terminating condition other than running out of data.
> Similarly, an improperly truncated "multipart" entity may not have
> any terminating boundary marker, and can turn up operationally due to
> mail system malfunctions.
> It is essential that such entities be handled correctly when they are
> themselves imbedded inside of another "multipart" structure. MIME
> implementations are therefore required to recognize outer level
> boundary markers at ANY level of inner nesting. It is not sufficient
> to only check for the next expected marker or other terminating
> condition.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
