On Wed, Jan 28, 2009 at 3:51 PM, William Lefkovics
<[email protected]> wrote:
> Interestingly, some mail clients barf at that subject.
Trying to enter it when sending a message, or trying to display it
when receiving? If an email client doesn't support MIME encoded
headers, then it properly should reject that subject when you try to
enter it, since it isn't ASCII. But if another email client receives
the header, and doesn't understand MIME encoded headers, it should
just display:
Subject:
=?utf-8?B?wr9sxLHJkMmvLcedIMm5b8mfIMedc24gb8qHIMm5x53Kh8mUyZDJucmQyaXJlCBw?=
=?utf-8?B?xLFsyZDKjCDJkCBzxLHJpcqHIHPEsQ==?=
For those of you playing along at home: The above is the encoded
form of the header, as actually transported. (I got it using "Show
original" in Google.) Unintelligible to us humans, but ASCII only,
and thus nominally compatible with 1982 era email systems. It's the
mail client's job to decode the above into the original Unicode.
But then, it wouldn't surprise me in the least to hear that some
clients attempt to decode the above, and then puke because they don't
handle it right. :)
-- Ben
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~ http://www.sunbeltsoftware.com/Ninja ~
