james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Wiederkehr (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] Commented: (MIME4J-34) o.a.j.m.message.Header#writeTo violates RFC 822
Date Sun, 01 Feb 2009 20:01:59 GMT

    [ https://issues.apache.org/jira/browse/MIME4J-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669434#action_12669434
] 

Markus Wiederkehr commented on MIME4J-34:
-----------------------------------------

The code fragment Robert referred to in his comment from 10/Feb/08 seems to have gone with
the "Second patch from MIM4J-5" (http://svn.apache.org/viewvc?view=rev&revision=674206).

Are there still any other round trip problems or can this issue be closed?

> o.a.j.m.message.Header#writeTo violates RFC 822
> -----------------------------------------------
>
>                 Key: MIME4J-34
>                 URL: https://issues.apache.org/jira/browse/MIME4J-34
>             Project: JAMES Mime4j
>          Issue Type: Bug
>    Affects Versions: 0.3, 0.4
>            Reporter: Oleg Kalnichevski
>            Assignee: Robert Burrell Donkin
>             Fix For: 0.6
>
>         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.


Mime
View raw message