From: Russ Allbery <rra@stanford.edu>
Subject: Re: nnml splitting on encoded headers
Date: Tue, 28 May 2002 17:31:36 -0700 [thread overview]
Message-ID: <ylg00b7q1j.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <wf18z64ar08.fsf@svelte.home> (Mark Thomas's message of "Tue, 28 May 2002 18:17:54 -0400")
Mark Thomas <swoon@bellatlantic.net> writes:
> Sometimes I get spam where the Content-Type is multipart/alternative
> and there is no charset listed in the headers. For these, I use the
> following rule to catch un-encoded spam:
> ("mail.spam.asian" "^subject:.*[¡-ÿ]\\{4,\\}")
> I figure any mail with more than four high-bit characters in a row in
> the subject is probably not one I'm going to be able to read.
I've had extremely good luck with the following regex:
.*[¹²³°¶÷¾].*
It still passes pretty much anything that's ISO 8859-1 or -15, and it
catches unencoded Korean and Cyrillic pretty reliably. Adjust to taste if
you get unencoded subject headers in character sets other than ISO 8859-1,
of course.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2002-05-29 0:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 20:10 Mark Thomas
2002-05-25 12:35 ` Mark Thomas
2002-05-25 17:25 ` Kai Großjohann
2002-05-26 0:00 ` Russ Allbery
2002-05-26 12:32 ` Mark Thomas
2002-05-30 22:21 ` Russ Allbery
2002-06-03 3:34 ` Jesper Harder
2002-06-03 17:52 ` Simon Josefsson
2002-06-03 19:41 ` Kai Großjohann
2002-06-03 19:48 ` Simon Josefsson
2002-06-03 20:04 ` Russ Allbery
2002-05-28 20:45 ` Norman Walsh
2002-05-28 22:17 ` Mark Thomas
2002-05-29 0:31 ` Russ Allbery [this message]
2002-05-29 7:39 ` Kai Großjohann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ylg00b7q1j.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).