[
https://issues.apache.org/jira/browse/MIME4J-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved MIME4J-130.
--------------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.8)
0.7
Markus, Robert,
I implemented a lenient version of AddressBuilder in the course of my work on
MIME4J-197. Please feel free to review / comment / critique.
Oleg
> Add parse method for e-mail addresses that contain special characters in the
> display name
> -----------------------------------------------------------------------------------------
>
> Key: MIME4J-130
> URL: https://issues.apache.org/jira/browse/MIME4J-130
> Project: JAMES Mime4j
> Issue Type: New Feature
> Affects Versions: 0.6
> Reporter: Markus Wiederkehr
> Fix For: 0.7
>
>
> Address.parse(), Group.parse() and Mailbox.parse() can only parse addresses
> in their raw (encoded) form. They are capable of decoding encoded words (RFC
> 2047) but they do not accept already decoded special characters.
> In other words, they can parse the result of Address.getEncodedString() but
> not Address.getDisplayString().
> Mime4j should have a means to parse an address such as "Hans Müller
> <[email protected]>" for generating new messages or manipulating existing
> ones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
