[
https://issues.apache.org/jira/browse/MIME4J-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565537#action_12565537
]
Robert Burrell Donkin commented on MIME4J-34:
---------------------------------------------
"as far as the strict interpretation of the MIME standard is concerned only
ASCII characters seem permissible"
yes
"and non-ASCII are expected to be escaped using BASE64 or Quoted-Printable
encodings."
no - AIUI non-ASCII header values not expected at all by the specification. i
do not know of any way for a client to discover such a transfer encoding.
there is considerable potential interoperability impact on email (where
international mail client often interpret the headers using the
content-encoding) by this patch.
- robert
> 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, 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]
