james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Wiederkehr (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] Commented: (MIME4J-181) AddressListParser should allow non ASCII characters in the name part of addresses
Date Wed, 10 Nov 2010 11:19:14 GMT

    [ https://issues.apache.org/jira/browse/MIME4J-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930575#action_12930575

Markus Wiederkehr commented on MIME4J-181:

To me this looks a bit like a duplicate of MIME4J-130. While the motivations behind the issues
are not the same they can probably be treated as one and be resolved together.

MIME4J-130 is more about creating new messages from scratch (e.g. the user enters an e-mail
address in a field and a message should be created for it).

This issue is more about parsing existing (but not well-formed) messages.

> 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 <hakan@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.

View raw message