Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
0.6
-
None
-
None
Description
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.