[
https://issues.apache.org/jira/browse/MIME4J-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara updated MIME4J-65:
----------------------------------
Attachment: MIME4J-65-complete.patch
This is a full patch for this issue.
The patch remove the usage of the Base64Encoder in favor of a
Base64OutputStream cloned by MyFaces Trinidad 1.2.8 (So it also solve MIME4J-66
and MIME4J-67).
It also adds a LineBreakerOutputStream to make sure the output from
Base64OutputStream is also splitted in 76 chars lines.
This also introduce a QuotedPrintableOutputStream based on the existing encoder.
The encoder has been refactored to expose the utility methods used by the
outputstream. The outputstream is not complete and only implements the used
method (bytes per bytes write is not supported).
This patch solve correctly and perfomantly this issue.
> Message.writeTo for an rfc822 part ignoring a "base64" encoding
> ---------------------------------------------------------------
>
> Key: MIME4J-65
> URL: https://issues.apache.org/jira/browse/MIME4J-65
> Project: Mime4j
> Issue Type: Bug
> Affects Versions: 0.4
> Reporter: Stefano Bagnara
> Fix For: 0.4, 0.5
>
> Attachments: MIME4J-65-complete.patch, MIME4J-65.patch,
> testmsgs-message-rfc822-encoding.zip
>
>
> the writeTo method for a Content-Transfer-Encoding: base64 and Content-Type:
> message/rfc822 part writes the message unencoded.
> I would expect it to be encoded in a base64 stream. See MIME4J-64 for an
> useful test.
--
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]
