Re: nnml splitting on encoded headers

[Norman Walsh <ndw@nwalsh.com>]

/ Mark Thomas <swoon@bellatlantic.net> was heard to say:
| I'd like to toss away mail that I know I'm not going to be able to
| read.
|
| I have split rules:
|   ("subject"  "=\\?euc-kr\\?"          "mail.spam.asian")
|   ("subject"  "=\\?ks_c_5601-1987\\?"  "mail.spam.asian")
| but these don't to work because Gnus has already decoded the messages.

/ Mark Thomas <swoon@bellatlantic.net> was heard to say:
| To answer my own question
|
| > Is there any way I can split on the non-decoded Subject header (the
| > Subject header I see when I C-u g the message)?
|
| (add-hook 'nnmail-split-hook 'rfc2047-encode-message-header)

These messages hint at a feature I would dearly love to have: the
ability to avoid mail in character sets I can't read. But I'm confused
by one part.

Looking at some representative asian spam on my machine, C-u g doesn't
display the encoding in the subject, instead I see things like this:

  Message-Id: <200205281859.OAA05629@nexus.berkshire.net>
  Reply-To: no@kojein.com
  From: ¿¹½º¸Ç<yes@kojein.com>
  To: ndw@nwalsh.com
  Subject: (±¸ÀÎ,±¤°í)ÀçÅþ˹٠ÇϽǺР
  Mime-Version: 1.0
  Content-Type: text/html; charset="ks_c_5601-1987"

Do the split rules shown above really match on the charset described
in Content-Type, or is there some other switch I have to enable to
make that appear literally in the subject?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Youth lasts much longer than young
http://nwalsh.com/            | people think.--Comtesse Diane