[jira] Updated: (MIME4J-65) Message.writeTo for an rfc822 part ignoring a "base64" encoding

["Stefano Bagnara (JIRA)" <se...@james.apache.org>]

     [ https://issues.apache.org/jira/browse/MIME4J-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefano Bagnara updated MIME4J-65:
----------------------------------

    Attachment: testmsgs-message-rfc822-encoding.zip
                MIME4J-65.patch

Added a patch (please note the patch produce correct results / fix the bug) but introduce memory/performance issues.

The full fix will require using outputstreams for the encoding, a input-output-pipe/worker pattern, or more custom code in Message.writeTo.

> 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.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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org