glassfishrobot

@bshannon Commented It's software, many things are *possible*. :-) Whose software created such a header? Did you report the bug to them? What did they say? This would be a...

@M-HT Commented I don't know what software created the header - there's no header identifying the email client. And I didn't contact any of the senders to inquire about it.

@sgumirov Commented I can confirm this decoding issue exists, I'm trying to resolve it when using Camel Mail endpoint

@bshannon Commented Can you determine which mailer created the message with the badly encoded header, e.g., by looking at the X-Mailer or User-Agent headers in the message? It would be...

* **Issue Imported From:** https://github.com/javaee/javamail/issues/101 * **Original Issue Raised By:**@glassfishrobot * **Original Issue Assigned To:** @bshannon

@glassfishrobot Commented @bshannon said: (Original evaluation from Sun bug system:) It's rarely necessary to create a new Session object for each message to be sent. Using a combination of the...

@glassfishrobot Commented Reported by @bshannon

@glassfishrobot Commented This issue was imported from Bugzilla JAVAMAIL-6278

* **Issue Imported From:** https://github.com/javaee/javamail/issues/197 * **Original Issue Raised By:**@glassfishrobot * **Original Issue Assigned To:** @bshannon

@glassfishrobot Commented @bshannon said: IMAP was designed around sequence numbers, and JavaMail follows that model. Changing JavaMail to allow you to operate using only UIDs without ever needing sequence numbers...