You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mime4j-dev@james.apache.org by "Niklas Therning (JIRA)" <mi...@james.apache.org> on 2010/11/03 11:53:25 UTC
[jira] Updated: (MIME4J-181) AddressListParser should allow non
ASCII characters in the name part of addresses
[ https://issues.apache.org/jira/browse/MIME4J-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niklas Therning updated MIME4J-181:
-----------------------------------
Attachment: mime4j.patch
Patch which adds a test method to AddressTest which demonstrates this bug.
> 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: Bug
> 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.