You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mime4j-dev@james.apache.org by "Robert Burrell Donkin (JIRA)" <mi...@james.apache.org> on 2009/02/04 21:52:01 UTC
[jira] Closed: (MIME4J-65) Message.writeTo for an rfc822 part
ignoring a "base64" encoding
[ https://issues.apache.org/jira/browse/MIME4J-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Burrell Donkin closed MIME4J-65.
---------------------------------------
Closing all issues fixed previously, after a brief review of each.
> Message.writeTo for an rfc822 part ignoring a "base64" encoding
> ---------------------------------------------------------------
>
> Key: MIME4J-65
> URL: https://issues.apache.org/jira/browse/MIME4J-65
> Project: JAMES Mime4j
> Issue Type: Bug
> Affects Versions: 0.4
> Reporter: Stefano Bagnara
> Assignee: Stefano Bagnara
> Fix For: 0.4
>
> 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.