[
https://issues.apache.org/jira/browse/JAMES-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747024#comment-13747024
]
Guillermo Grandes commented on JAMES-1518:
------------------------------------------
Maybe you want see jira issues [JAMES-648] and [JAMES-642]
And as a comment if finally allows accept non-RFC headers:
>From "Standards compliance":
http://james.apache.org/server/design_objectives.html
{quote}In cases (like jira issue JAMES-344) where variance from a published
standard is required it is desirable that this functionality is disabled in
James by default, it must be prominently and clearly documented that this
causes James to violate the relevant standard, and should be enabled by
explicit configuration, making its use a conscious decision of the user rather
than an decision taken by the James team{quote}
> Allows non-ASCII characters in MIME mail headers
> ------------------------------------------------
>
> Key: JAMES-1518
> URL: https://issues.apache.org/jira/browse/JAMES-1518
> Project: James Server
> Issue Type: Improvement
> Components: James Core
> Reporter: TzeKai Lee
> Attachments: spl-1.txt, use-8859.patch
>
>
> Currently any non-ASCII characters in MIME header contains byte > 127 will be
> converted to '?' (ascii 63).
> Can we pass these kind characters as it is instead of converted to '?' ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
