[
https://issues.apache.org/jira/browse/MIME4J-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565749#action_12565749
]
Stefano Bagnara commented on MIME4J-34:
---------------------------------------
The base64 and quoted-printable IMHO refers to RFC2047
(http://www.faqs.org/rfcs/rfc2047.html).
The format for the encoded header values is:
=?#charset#?#encoding#?#encoded-text#?=
I don't know what is the client support for other headers, but it works for
Subjects.
I know of some mailers (MUA) that only recognize this format only when it is
used for the WHOLE header value and not for the single encoded word.
Some mailer (MUA) also accept 8bit data in the headers and threat them using
the same charset declared by the headers. This is not an RFC compliant
behaviour, but I think this happened very much in oriental countries in the
past years so many MUA supports this to increase the compatibility with "badly
formatted" emails.
IMHO a "leave as is" option should be made available. Sometimes we want to
alter a message adding some header without altering any other bit. (maybe this
is your "international-lenient content+IGNORE" ?).
> 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]
