[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: charset=ks_c-5601_1987
On Mon, Feb 11, 2002 at 08:34:27PM +0100, Erika Pacholleck wrote:
> ------=_NextPart_000_0007_01C0F27A.93A50C00
> Content-Type: text/plain;
> charset="ks_c_5601-1987"
> Content-Transfer-Encoding: base64
[...]
> Normally I pipe those mails through /dev/null which will
> keep my eyes unhurt but that obviously does not clear
> whether it is me or the sender who is not able to use
> proper charsets in MUAs ;)
The complete list of mail-legal charsets is at <http://www.iana.org>
(Proctocol numbers, charsets). As you can see, ks_c_5601-1987 is
registered, and it's Korean. A description is available in RFC 1345.
While it is legal, it's probably not something that you need to worry
about. In a discussion of spam, a Korean Debian maintainer recommended
dropping all messages using this charset; according to him, any real
Korean mail comes with a different charset, usually ISO-2022-KR (IIRC).
I've been redirecting mail with this charset to a spam folder for a
while, and never found something that looked misdirected due to that,
and a number of things that it caught.
--
David Starner / Давид Старнзр - starner@xxxxxxxxxxx
Pointless website: http://dvdeug.dhis.org
What we've got is a blue-light special on truth. It's the hottest thing
with the youth. -- Information Society, "Peace and Love, Inc."
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/