[
https://issues.apache.org/jira/browse/MIME4J-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795309#action_12795309
]
Stefano Bagnara commented on MIME4J-152:
----------------------------------------
It seems we can remove T_IN_MESSAGE and T_IN_BODYPART states and simply
EntityStates.T_BODY (instead of T_IN_MESSAGE) and EntityStates.T_PREAMBLE
(instead of T_IN_BODYPART). At least this work fine in my uncommitted code.
> Zero parts multipart messages are parsed as 1 empty part multipart messages
> ---------------------------------------------------------------------------
>
> Key: MIME4J-152
> URL: https://issues.apache.org/jira/browse/MIME4J-152
> Project: JAMES Mime4j
> Issue Type: Bug
> Affects Versions: 0.6
> Reporter: Stefano Bagnara
> Assignee: Stefano Bagnara
> Priority: Minor
> Fix For: 0.8
>
> Attachments: testmsgs-missingboundaries.zip
>
>
> Mime4j currenlty parse a message having only the start boundary as an empty
> message (zero parts) but at the same time parse a message with no boundary
> (no start and no end) as a message with 1 empty part.
> This is clearly wrong.
> We also already have a missing-inner-boundary.msg in our testsuite but the
> expectation files are wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
