[
https://issues.apache.org/jira/browse/MIME4J-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara updated MIME4J-84:
----------------------------------
Attachment: mime4j-base64-one-lf.patch
mime4j-base64-one-lf-testmsgs.zip
Markus said:
--------
The patch is pretty straightforward. The only noteworthy thing is that
the last line of base64encoded-rfc822message-nested.out changes from
..PT0NCg0K to ..PT0NCg==. This is because there is another base64
block encoded into this block that also changes.
> Base64OutputStream and trailing CRLFs
> -------------------------------------
>
> Key: MIME4J-84
> URL: https://issues.apache.org/jira/browse/MIME4J-84
> Project: JAMES Mime4j
> Issue Type: Bug
> Affects Versions: 0.5
> Reporter: Stefano Bagnara
> Fix For: 0.6
>
> Attachments: mime4j-base64-one-lf-testmsgs.zip,
> mime4j-base64-one-lf.patch
>
>
> Markus said:
> ----
> the current implementation adds two line feed at the end of a
> base64 encoded block. In a multipart/mixed message this leads to two
> empty lines between a base64 block and the following boundary string.
> This is only a minor issue but it is not the way it should be.
> Here is a patch that would resolve the issue.
> ----
> PS: Markus discussed this issue with me via email. I don't have time to check
> it now, so I create this JIRA to not loose it.
--
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]
