james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burrell Donkin (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] Resolved: (MIME4J-34) o.a.j.m.message.Header#writeTo violates RFC 822
Date Fri, 06 Feb 2009 21:08:59 GMT

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

Robert Burrell Donkin resolved MIME4J-34.
-----------------------------------------

    Resolution: Fixed

This issue has been substantially addressed. Some tidying up and verification testing is required
but this will be left until the next release.

> 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