[jira] Updated: (MIME4J-34) o.a.j.m.message.Header#writeTo violates RFC 822

["Oleg Kalnichevski (JIRA)" <se...@james.apache.org>]

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

Oleg Kalnichevski updated MIME4J-34:
------------------------------------

    Attachment: mimeheader.patch

The new version of the patch adds support for different protocol compliance levels:

* STRICT_ERROR: ASCII charset is used when writing out multipart boundary elements; the use of invalid characters causes an MimeException  
* STRICT_IGNORE: ASCII charset is used when writing out multipart boundary elements; invalid characters are silently ignored (replaced with ?)
* LENIENT: content charset is used when writing out multipart boundary elements;

Lenient mode is used per default.

Please review and let me know what you think

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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org