Bill Shannon
Bill Shannon
An address that contains non-ASCII characters is not a valid RFC 822 address. The InternetAddress(String) constructor and the parse(String) method require a valid RFC 822 address. What version of JavaMail...
Right, non-ASCII has to be encoded for RFC 822, your example is not. I still get the exception with JavaMail 1.4.6 (which is 6 years old). $ cat iatest.java import...
The single argument constructor takes an RFC 822 formatted address, which can include both an email address and a personal name field. The key is that the argument needs to...
Ok, now we're getting somewhere... If you already have the display name and the email address as separate strings, you should clearly use the constructor that takes them as separate...
I wouldn't normally expect a user to type in an email address in that format since it's very likely that they would get the syntax wrong. Normally I would expect...
I still need an example of a message to has this problem. Please post the raw MIME content of such a message. Most likely the message was incorrectly encoded. You...
Yes, you're right, thanks!
Unfortunately, fixing this causes the TCK to fail, so this fix will need to be deferred until the TCK can be fixed as well. In the mean time, the server...
JavaMail should have been emitting ISO standard charset names from the beginning, at least for most charsets. JavaMail includes a mapping table to map from the old JDK charset names...
It is possible that old versions of JavaMail did not apply the mapping correctly, but no reproducible bug has been reported. And of course it's possible that some application is...