Re: [WL] Re[2]: [SAtalk] Character Set Spam....

2003-11-22 Thread Charles Gregory
On Fri, 21 Nov 2003, Robert Menschel wrote: > I use the following rule with some success. You should be able to > substitute your windows-1251. > header RM_sx_iso8859 Subject:raw =~ /iso-8859-1/i Interesting. They do not list the 'raw' option in the SA documentation for header checks. This is

Re: [WL] Re: [SAtalk] Character Set Spam....

2003-11-22 Thread Charles Gregory
On Fri, 21 Nov 2003, Justin Mason wrote: > Charles Gregory writes: > >I've been playing with the 'locales' settings, and they work quite well > >where a message has been properly formatted with 'charset' headers, but > >here's a message whose only visible clue is the use of 'windows-1251' in > >the

Re[2]: [SAtalk] Character Set Spam....

2003-11-21 Thread Robert Menschel
JM> Charles Gregory writes: >>I've been playing with the 'locales' settings, and they work quite well >>where a message has been properly formatted with 'charset' headers, but >>here's a message whose only visible clue is the use of 'windows-1251' >>in the SUBJECT line. The text is obviously a non

Re: [SAtalk] Character Set Spam....

2003-11-21 Thread Justin Mason
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charles Gregory writes: >Hello! > >I've been playing with the 'locales' settings, and they work quite well >where a message has been properly formatted with 'charset' headers, but >here's a message whose only visible clue is the use of 'windows-1251'

[SAtalk] Character Set Spam....

2003-11-21 Thread Charles Gregory
Hello! I've been playing with the 'locales' settings, and they work quite well where a message has been properly formatted with 'charset' headers, but here's a message whose only visible clue is the use of 'windows-1251' in the SUBJECT line. The text is obviously a non-English characterset, but I