Circa 2001-Nov-16 12:34:59 -0500 dixit Greg Ward:
: Hi all --
:
: This is not *really* an Exim question, but this list has a lot of
: collective RFC (2)822 expertise, so I thought I'd bring this up as a
: point of curiosity.
:
: A mailing list we run recently received a legitimate, non-spam message
: with the following headers:
:
: MIME-Version: 1.0
: Message-Id: <3BF4D342.24968@mta4>
: Content-Type: text/plain; charset="us-ascii"
: Date: Fri, 16 Nov 2001 16:50:10 +0800 (CST)
: From: dchli@???
: To: mems-talk@???
: Subject: =?gb2312?B?TUVNUyBUZXN0aW5nIQ==?=
^^^^^^
: X-Originating-IP: [162.105.201.36]
: X-Mailer: Coremail2.0 Copyright Tebie Ltd., 2001
: X-Converted-To-Plain-Text: from Multipart/Alternative by demime 0.98e
: X-Converted-To-Plain-Text: Alternative section used was text/plain
:
: Note the garbled subject line.
:
: Can anyone explain what encoding is being used in this subject line? It
: *looks* like base64, but I tried running it through Python's base64
: module, and it complained of incorrect padding.
It's RFC-2047 header encoding. The bit i underscored above is the
character set, GB-2312, which is defined in RFC-1842.
http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc2047.html
http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1842.html
--
jim knoble | jmknoble@??? |
http://www.pobox.com/~jmknoble/
(GnuPG fingerprint: 31C4:8AAC:F24E:A70C:4000::BBF4:289F:EAA8:1381:1491)
