Since bug 384716 is marked as a duplicate, commenting here.
The problem reported in 384716 is definitely have nothing to do with sender address, but rather IMAP decoding.
In my case, problem triggered on e-mails from exactly one person and only using IMAP provided by safesecureweb.com mail hosting.
$ telnet mail36.safesecureweb.com imap
Connected to mail36.safesecureweb.com.
Escape character is '^]'.
* OK IMAP4rev1 SmarterMail
GMail IMAP brings these very same messages absolutely ok.
If needed, I can try to arrange an account for testing. Although, not 100% sure.
Please contact me directly for this via dmelentyev AT dynamo-ny DOT com.
Since bug 384716 is marked as a duplicate, commenting here.
The problem reported in 384716 is definitely have nothing to do with sender address, but rather IMAP decoding.
In my case, problem triggered on e-mails from exactly one person and only using IMAP provided by safesecureweb.com mail hosting.
$ telnet mail36. safesecureweb. com imap safesecureweb. com.
Connected to mail36.
Escape character is '^]'.
* OK IMAP4rev1 SmarterMail
GMail IMAP brings these very same messages absolutely ok.
If needed, I can try to arrange an account for testing. Although, not 100% sure.
Please contact me directly for this via dmelentyev AT dynamo-ny DOT com.