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 "Oleg Kalnichevski (JIRA)" <mi...@james.apache.org> on 2011/06/15 11:54:47 UTC

[jira] [Resolved] (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 ]

Oleg Kalnichevski resolved MIME4J-181.
--------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.8)
                   0.7

One can now use LenientFieldParser instead of DefaultFieldParser when a more relaxed handling of address fields is desired.

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
>             Fix For: 0.7
>
>         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.
For more information on JIRA, see: http://www.atlassian.com/software/jira