[
https://issues.apache.org/jira/browse/MIME4J-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara updated MIME4J-54:
----------------------------------
Attachment: testmsgs-endingboundaries-complete.zip
MIME4J-54-complete.patch
Updated code and updated tests.
Now after a boundary is found we skip and *IGNORE* anything until we find a
newline.
Please note I incorporated skipNewLine in skipBoundary and I also had to move
the if (eof) check just before the fillBuffer because it was not skipping
anything in the case the buffer was already the last for the stream (maybe this
was another bug, but I'm not sure).
> boundaries should only be found at the beginning of a line
> ----------------------------------------------------------
>
> Key: MIME4J-54
> URL: https://issues.apache.org/jira/browse/MIME4J-54
> Project: Mime4j
> Issue Type: Bug
> Affects Versions: 0.4
> Reporter: Stefano Bagnara
> Fix For: 0.4
>
> Attachments: boundary-tests.zip, MIME4J-54-complete.patch,
> MIME4J-54.patch, testmsgs-endingboundaries-complete.zip
>
>
> current mime4j seems to be fooled by mime boundaries inside lines of text
> parts (not at the beginnning of a line).
> I committed misplaced-boundary.msg example message to show the issue and the
> expected result.
--
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]
