james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitsan Seniak (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] [Commented] (MIME4J-239) AddressBuilder#parseMailbox fails when the local part contains a '@'
Date Sat, 14 Jun 2014 20:33:01 GMT

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

Nitsan Seniak commented on MIME4J-239:
--------------------------------------

"I understand why this might not be a bug" => what I meant is that Stefano's explanation
made me understand this is not a bug. I did not intentionally enter this as a bug knowing
it isn't one.

Although it's not a bug it still seems to be a problem because apparently there are emails
with such addresses circulating around, and my system is probably not the only one receiving
them.

Is there a workaround, like a way to catch malformed addresses in mime headers and handle
them with custom code?

Any help would be greatly appreciated.


> AddressBuilder#parseMailbox fails when the local part contains a '@'
> --------------------------------------------------------------------
>
>                 Key: MIME4J-239
>                 URL: https://issues.apache.org/jira/browse/MIME4J-239
>             Project: James Mime4j
>          Issue Type: Bug
>    Affects Versions: 0.7.2
>            Reporter: Nitsan Seniak
>            Priority: Critical
>
> The following calls throws an exception:
> Mailbox add = AddressBuilder.DEFAULT.parseMailbox("joe@my company <joe.foo@company.com>");
> The exception is:
> org.apache.james.mime4j.field.address.ParseException: Atoms in domain names must be separated
by '.'
> The expected result is (Hamcrest syntax):
> Mailbox add = AddressBuilder.DEFAULT.parseMailbox("joe@my company <joe.foo@company.com>");
> assertThat(add.getAddress(), is("joe.foo@company.com"));
> assertThat(add.getLocalPart(), is("joe@my company"));



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message