[
https://issues.apache.org/jira/browse/MIME4J-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567075#action_12567075
]
Oleg Kalnichevski commented on MIME4J-34:
-----------------------------------------
> The strictly correct approach would be to create a charset implementation
> that understood how to encode and decode this syntax.
Robert,
I am not sure that would work, as the encoding is meant to apply to message
elements such as header bodies, and not the whole data stream.
> Maybe geronimo has its owm implementation of MailUtility?
Stefano,
Just for the record, Commons Codec provides both Base64 and quoted-printable
codes. Unfortunately Codec cannot work with streams, but this does not seem to
be very relevant in this particular case.
Oleg
> o.a.j.m.message.Header#writeTo violates RFC 822
> -----------------------------------------------
>
> Key: MIME4J-34
> URL: https://issues.apache.org/jira/browse/MIME4J-34
> Project: Mime4j
> Issue Type: Bug
> Affects Versions: 0.3
> Reporter: Oleg Kalnichevski
> Attachments: mimeheader.patch
>
>
> The Header#writeTo method uses the content charset instead of US-ASCII
> required by the RFC 822. Same problem exists in the Multipart#writeTo.
--
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]
