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 "Markus Wiederkehr (JIRA)" <mi...@james.apache.org> on 2009/04/22 16:15:47 UTC
[jira] Created: (MIME4J-130) Add parse method for e-mail addresses
that contain special characters in the display name
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
Assignee: 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 <ha...@acme.com>" for generating new messages or manipulating existing ones.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MIME4J-130) Add parse method for e-mail
addresses that contain special characters in the display name
Posted by "Markus Wiederkehr (JIRA)" <mi...@james.apache.org>.
[ https://issues.apache.org/jira/browse/MIME4J-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701540#action_12701540 ]
Markus Wiederkehr commented on MIME4J-130:
------------------------------------------
I'm not such what would be the best approach for this problem. Is it possible and reasonable to modify the existing JavaCC address list parser (AddressListParser.jjt) to accept both forms? Or does a new parser have to be written (maybe by copying and adapting AddressListParser.jjt)?
> 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
> Assignee: 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 <ha...@acme.com>" for generating new messages or manipulating existing ones.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (MIME4J-130) Add parse method for
e-mail addresses that contain special characters in the display name
Posted by "Markus Wiederkehr (JIRA)" <mi...@james.apache.org>.
[ https://issues.apache.org/jira/browse/MIME4J-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701540#action_12701540 ]
Markus Wiederkehr edited comment on MIME4J-130 at 4/22/09 7:30 AM:
-------------------------------------------------------------------
I'm not sure what would be the best approach for this problem. Is it possible and reasonable to modify the existing JavaCC address list parser (AddressListParser.jjt) to accept both forms? Or does a new parser have to be written (maybe by copying and adapting AddressListParser.jjt)?
was (Author: wmax):
I'm not such what would be the best approach for this problem. Is it possible and reasonable to modify the existing JavaCC address list parser (AddressListParser.jjt) to accept both forms? Or does a new parser have to be written (maybe by copying and adapting AddressListParser.jjt)?
> 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
> Assignee: 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 <ha...@acme.com>" for generating new messages or manipulating existing ones.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MIME4J-130) Add parse method for e-mail addresses
that contain special characters in the display name
Posted by "Markus Wiederkehr (JIRA)" <mi...@james.apache.org>.
[ https://issues.apache.org/jira/browse/MIME4J-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Wiederkehr updated MIME4J-130:
-------------------------------------
Fix Version/s: (was: 0.7)
0.8
Assignee: (was: Markus Wiederkehr)
> 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.8
>
>
> 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 <ha...@acme.com>" for generating new messages or manipulating existing ones.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MIME4J-130) Add parse method for e-mail
addresses that contain special characters in the display name
Posted by "Robert Burrell Donkin (JIRA)" <mi...@james.apache.org>.
[ https://issues.apache.org/jira/browse/MIME4J-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701541#action_12701541 ]
Robert Burrell Donkin commented on MIME4J-130:
----------------------------------------------
+1
- robert
> 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
> Assignee: 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 <ha...@acme.com>" for generating new messages or manipulating existing ones.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MIME4J-130) Add parse method for e-mail
addresses that contain special characters in the display name
Posted by "Markus Wiederkehr (JIRA)" <mi...@james.apache.org>.
[ https://issues.apache.org/jira/browse/MIME4J-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701538#action_12701538 ]
Markus Wiederkehr commented on MIME4J-130:
------------------------------------------
We could add methods such as Address.for(String), Group.for(String) and Mailbox.for(String) for this purpose.
> 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
> Assignee: 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 <ha...@acme.com>" for generating new messages or manipulating existing ones.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.