.....w¡ñ§±¤ñ wrote:
VVVVVVVVVVV Incorrect UTF8 Base64 corrected to his all-ASCII nym is:
....winston

From: =?UTF-8?B?Li4uLnfCocOxwqfCscKkw7E=?=

Seamonkey is screwing up your nym in the From header even worse than
whatever you were using before. The decoding of your UTF-8 Base64 nym
shows the original string had non-ASCII characters. Why do you need
UTF8 B64 encoding when "...winston" consists of ten ASCII characters?

"...winston" (sans quotes) in UTF-8 Base64 is encoded as:
=?UTF-8?B?Li4ud2luc3Rvbg==?=
not as
=?UTF-8?B?Li4uLnfCocOxwqfCscKkw7E=?=

Test it out at http://www.sendblaster.com/en/utf8-e...ubject-encoder.
Enter "...winston" to see what the UTF-8 Base64 string should be. As
another test, go to http://dogmamix.com/MimeHeadersDecoder/ and enter
what Seamonkey put in your From header, which was:

From: =?UTF-8?B?Li4uLnfCocOxwqfCscKkw7E=?=

and click the Decode button. Instead of "...winston" as your nym, it
decodes to "....w¡ñ§±¤ñ" (with 4 leading dots instead of 3).