[
https://issues.apache.org/jira/browse/MIME4J-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613295#action_12613295
]
Oleg Kalnichevski commented on MIME4J-52:
-----------------------------------------
I'll look into fixing the infinite loop. Unfortunately I do not see an easy way
of fixing the way corrupt multipart entities are parsed. The parser in its
present form tracks only one boundary at a time. It can't resume looking for
the outer boundary until the inner one is properly terminated. This approach
has its advantages and disadvantages: on the plus side it is more efficient
both in terms performance and the memory footprint. Also, the parser can handle
correctly inner body parts that may accidentally contain the outer boundary. On
the negative side, malformed multipart entities mess the rest of the message up
completely.
Oleg
> Infinite loop when nested multipart is missing end boundary
> -----------------------------------------------------------
>
> Key: MIME4J-52
> URL: https://issues.apache.org/jira/browse/MIME4J-52
> Project: Mime4j
> Issue Type: Bug
> Affects Versions: 0.4
> Reporter: Niklas Therning
> Fix For: 0.4
>
> Attachments: 36387089_3.msg
>
>
> I'm attaching a message which causes Mime4j to loop indefinitely in
> non-strict mode. The message contains badly formatted MIME. The inner
> multipart has no end boundary. Mime4j 0.3 handled this situation without any
> problems. The inner multipart would stop at --outer boundary-- and the AAA
> would be part of the preamble for the inner multipart.
--
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]
