[
https://issues.apache.org/jira/browse/MIME4J-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated MIME4J-181:
-------------------------------------
Issue Type: Improvement (was: Bug)
I personally do not think it is a bug, thought, I also would like the
AddressListParser to be more lenient about non-ASCII characters in the
display-name. Unfortunately it appears that the fix for the issue may require a
fair number of declarations in the jjtree file to be duplicated (one for
ASCII-only constructs and another one for those where non-ASCII characters are
permitted)
Admittedly I know next to nothing about JJTREE, so, ideally someone with a
better understanding of jjtree should take a look.
Oleg
> AddressListParser should allow non ASCII characters in the name part of
> addresses
> ---------------------------------------------------------------------------------
>
> Key: MIME4J-181
> URL: https://issues.apache.org/jira/browse/MIME4J-181
> Project: JAMES Mime4j
> Issue Type: Improvement
> Components: dom
> Affects Versions: 0.7
> Reporter: Niklas Therning
> Attachments: mime4j.patch
>
>
> Seems quite common that user agents don't encode From: and Sender: fields
> properly. This means that they contain non ASCII characters. E.g. "From:
> Håkan Öster <ha...@example.net>". It would be nice if Mime4j could handle
> these addresses without a parse error at least in non strict mode. Right now
> AddressListParser fails with a ParseException because it only allows ASCII
> characters.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
