On Tue, Mar 05, 2002 at 02:08:39AM -0800, Matthew Cline wrote:
| For those of you who find that English-centricity helps to filter spam,
| here's a rule that looks for non-ASCII encoding in the subject line:
|
| header NON_ASCII_ENC_SUBJ Subject =~ /=\?(?:euc-kr|big5|iso-8859-1)\?/
| describe NON_ASCII_ENC_SUBJ Non-ASCII encoded subject
|
| It just does EUC Korean, Big5 Chinese and ISO Western encodings now, but it's
| easy enough to add other encodings.
These are supposed to be caught by the CHARSET_FARAWAY family of
tests. Maybe those are not working now? I've seen lots of
ks_c_5601-1987 encoded stuff slide right by them. My solution to that
was to add my own test explicitly for that. I also made one for the
"=?UNKNOWN?" encoding of headers as an "unknown" charset is quite
useless!
-D
--
A wise servant will rule over a disgraceful son,
and will share the inheritance as one of the brothers.
Proverbs 17:2
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
