>I'm not an expert, but it may be that this started as a way to encode
>languages containing Unicode into RFC-compliant messages. When I created my
>own text kill filters for this it caught some E-mails that looked legitimate
>to a business that did foreign correspondance (I didn't decode or analyze
>them in detail though).
That *shouldn't* happen, if the E-mail was using a "text/plain" or
"text/html" MIME segment. The "text/plain" should only be used for ASCII
data, and "text/html" should only be used for HTML.
I'm guessing that either [1] They had no clue what they were doing, and
sent Unicode in a text/plain MIME segment, which isn't supposed to happen,
or [2] It may have actually been a different MIME type ("text/unicode",
perhaps -- I don't know).
If you (or anyone else) happens to have one of these, I would be interested
in seeing it.
-Scott
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
