[
https://issues.apache.org/jira/browse/MIME4J-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616210#action_12616210
]
Stefano Bagnara commented on MIME4J-34:
---------------------------------------
I think the title of this issue is too generic: can anyone update this
according to the specific issue and the current mime4j status?
The fact that writeTo produces sequences violating the rfc822 is also discussed
in MIME4J-60 (even if MIME4J-60 should be probably splitted in parsing issues
and DOM's writeTo issues).
> 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, 0.4
> Reporter: Oleg Kalnichevski
> Assignee: Robert Burrell Donkin
> Fix For: 0.5
>
> 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]
