You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Mike Pepe <la...@doki-doki.net> on 2008/03/19 17:17:31 UTC
Cyrillic spam
For some strange reason, I'm seeing Cyrillic spams very frequently lately.
None of my users read any Eastern European languages- is there a quick
way to catch these?
thanks
-Mike
Re: Cyrillic spam
Posted by Matus UHLAR - fantomas <uh...@fantomas.sk>.
On 19.03.08 09:17, Mike Pepe wrote:
> For some strange reason, I'm seeing Cyrillic spams very frequently lately.
>
> None of my users read any Eastern European languages- is there a quick
> way to catch these?
configure properly ok_locales (it defines charsets in which you accept
e-mail) and optionally ok_languages (the same for languages, needs TextCat
plugin loaded).
--
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"The box said 'Requires Windows 95 or better', so I bought a Macintosh".
RE: Re: Cyrillic spam
Posted by Michael Hutchinson <mh...@manux.co.nz>.
> -----Original Message-----
> From: news [mailto:news@ger.gmane.org] On Behalf Of NFN Smith
> Sent: Thursday, 20 March 2008 1:54 p.m.
> To: users@spamassassin.apache.org
> Subject: Re: Cyrillic spam
>
> Michael Hutchinson wrote:
> >> -----Original Message-----
> >> From: Mike Pepe [mailto:lamune@doki-doki.net]
> >> Sent: Thursday, 20 March 2008 5:18 a.m.
> >> To: users@spamassassin.apache.org
> >> Subject: Cyrillic spam
> >>
> >> For some strange reason, I'm seeing Cyrillic spams very frequently
> > lately.
> >> None of my users read any Eastern European languages- is there a
quick
> >> way to catch these?
> >>
> >> thanks
> >>
> >> -Mike
> >
> > You could use the ok_languages and ok_locales settings. I'm sure
> > discussions on those can be found in the archives.
> >
> > I employed these rules for my site:
>
> I'll have to check those myself.
>
> Since I do have users that get Cyrillic content, I have to include
> Cyrillic in my ok_locales.
>
> I did a simple header rule that does a raw search for koi-8 . From
> there, I did a couple of meta rules that give big scores to the
> combination of Cyrillic plus at least one of: The Bat! as the sending
> client, or SPAMMY-XMAILER or OUTLOOK_3416 and gave suitably high
scores.
> My Cyrillic spam has pretty much vanished.
>
> Before I implemented these, I checked with my users who do Cyrillic,
and
> have no complaints from them since implementing. Even though there is
a
> Russian spell-checking module for The Bat!, as far as I can tell none
of
> my users exchange mail with Russian-speaking users of The Bat!
>
> It's been discussed in this list before that going after content with
> The Bat! is dangerous, because it's a legitimate client, but among my
> users, the frequency of inbound mail with The Bat! is virtually zero.
> Thus, although I score 2.1 points for The Bat!, I tend to use that
rule
> frequently in metas that combine with other more frequently hit rules.
>
> To me, this is some of the real elegance of SpamAssassin, in that you
> can score some number of common patterns with low scores, and beyond
the
> cumulative score of what turns up, using meta rules to look for
> combinations of this, this and that (and when that particular
> combination gets a hit, assign suitable high scores) is really useful.
If there was a book, you've done your config by it. It's good to see
other people using Meta's, they absolutely rock, and it's a good way to
avoid FP's, as you've already proven.
Cheers,
Mike
Re: Cyrillic spam
Posted by NFN Smith <wo...@sacbeemail.com>.
Michael Hutchinson wrote:
>> -----Original Message-----
>> From: Mike Pepe [mailto:lamune@doki-doki.net]
>> Sent: Thursday, 20 March 2008 5:18 a.m.
>> To: users@spamassassin.apache.org
>> Subject: Cyrillic spam
>>
>> For some strange reason, I'm seeing Cyrillic spams very frequently
> lately.
>> None of my users read any Eastern European languages- is there a quick
>> way to catch these?
>>
>> thanks
>>
>> -Mike
>
> You could use the ok_languages and ok_locales settings. I'm sure
> discussions on those can be found in the archives.
>
> I employed these rules for my site:
I'll have to check those myself.
Since I do have users that get Cyrillic content, I have to include
Cyrillic in my ok_locales.
I did a simple header rule that does a raw search for koi-8 . From
there, I did a couple of meta rules that give big scores to the
combination of Cyrillic plus at least one of: The Bat! as the sending
client, or SPAMMY-XMAILER or OUTLOOK_3416 and gave suitably high scores.
My Cyrillic spam has pretty much vanished.
Before I implemented these, I checked with my users who do Cyrillic, and
have no complaints from them since implementing. Even though there is a
Russian spell-checking module for The Bat!, as far as I can tell none of
my users exchange mail with Russian-speaking users of The Bat!
It's been discussed in this list before that going after content with
The Bat! is dangerous, because it's a legitimate client, but among my
users, the frequency of inbound mail with The Bat! is virtually zero.
Thus, although I score 2.1 points for The Bat!, I tend to use that rule
frequently in metas that combine with other more frequently hit rules.
To me, this is some of the real elegance of SpamAssassin, in that you
can score some number of common patterns with low scores, and beyond the
cumulative score of what turns up, using meta rules to look for
combinations of this, this and that (and when that particular
combination gets a hit, assign suitable high scores) is really useful.
Smith
Re: Cyrillic spam
Posted by Matus UHLAR - fantomas <uh...@fantomas.sk>.
> > that should be enough imho. CHARSET_FARAWAY with UNWANTED_LANGUAGE give
> > scores high enough to be marked as spam..
On 25.03.08 09:11, Michael Hutchinson wrote:
> That sounds great.
> > I wonder why didn't you use the former? and also, why do you add score
> > of 6.6 ?
[...]
> > > These two rules should tag your Cyrillic spam just fine. You might
> > > prefer to throw the language away entirely with the ok_languages
> etc.
> > > Just depends how you want to go about it.
> >
> > the ok_* don't "throw anything entirely", they only score unwanted
> > charsets
> > and languagees.
>
> Ok so the wording may have been incorrect, but as far as the end-user is
> concerned, it is being thrown away, as their filters (at least on our
> sites) prevent them from seeing anything tagged with 5 or more points.
>
> Anyway, lets stop barking up my rules, and agree there's more than one
> way to do it, and my way works for my site and your way works for your
> site.
I didn't want to bark at your rules, just note that there might be a safer
way to make them, e.g. making more rules with lower scores match, instead of
less rules with high scores. I hope you won't meet FP's soon ;)
--
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
I wonder how much deeper the ocean would be without sponges.
RE: Cyrillic spam
Posted by Michael Hutchinson <mh...@manux.co.nz>.
> -----Original Message-----
> From: Matus UHLAR - fantomas [mailto:uhlar@fantomas.sk]
> Sent: Friday, 21 March 2008 3:28 a.m.
> To: users@spamassassin.apache.org
> Subject: Re: Cyrillic spam
>
> > > For some strange reason, I'm seeing Cyrillic spams very frequently
> > > lately.
> > >
> > > None of my users read any Eastern European languages- is there a
quick
> > > way to catch these?
>
> On 20.03.08 08:54, Michael Hutchinson wrote:
> > You could use the ok_languages and ok_locales settings. I'm sure
> > discussions on those can be found in the archives.
>
> that should be enough imho. CHARSET_FARAWAY with UNWANTED_LANGUAGE
give
> scores high enough to be marked as spam..
That sounds great.
> > I employed these rules for my site:
> >
> > header CST_RUSSIANSPAM1 Subject:raw =~
> > /\=\?(koi8\-r|windows\-125[0125]|windows\-874|iso\-8859\-[28])\?/i
> > score CST_RUSSIANSPAM1 6.6
> > describe CST_RUSSIANSPAM1 Russian SPAM, trap Subject line for
> > language set
> >
> > header CST_RUSSIANSPAM2 From:raw =~
> > /\=\?(koi8\-r|windows\-125[0125]|windows\-874|iso\-8859\-[28])\?/i
> > score CST_RUSSIANSPAM2 6.6
> > describe CST_RUSSIANSPAM2 Russian SPAM, trap From line for
> > language set
>
> I wonder why didn't you use the former? and also, why do you add score
of
> 6.6 ?
The rules caught all of the Russian Spam our site was receiving, so I
decided to push the score high enough that it would always be tagged as
spam, no matter what route it took. I also thought it would be a good
idea to understand some not-so-simple rule writing for Subject and From
Email headers...
> > These two rules should tag your Cyrillic spam just fine. You might
> > prefer to throw the language away entirely with the ok_languages
etc.
> > Just depends how you want to go about it.
>
> the ok_* don't "throw anything entirely", they only score unwanted
> charsets
> and languagees.
Ok so the wording may have been incorrect, but as far as the end-user is
concerned, it is being thrown away, as their filters (at least on our
sites) prevent them from seeing anything tagged with 5 or more points.
Anyway, lets stop barking up my rules, and agree there's more than one
way to do it, and my way works for my site and your way works for your
site.
Cheers,
Mike
Re: Cyrillic spam
Posted by Matus UHLAR - fantomas <uh...@fantomas.sk>.
> > For some strange reason, I'm seeing Cyrillic spams very frequently
> > lately.
> >
> > None of my users read any Eastern European languages- is there a quick
> > way to catch these?
On 20.03.08 08:54, Michael Hutchinson wrote:
> You could use the ok_languages and ok_locales settings. I'm sure
> discussions on those can be found in the archives.
that should be enough imho. CHARSET_FARAWAY with UNWANTED_LANGUAGE give
scores high enough to be marked as spam..
> I employed these rules for my site:
>
> header CST_RUSSIANSPAM1 Subject:raw =~
> /\=\?(koi8\-r|windows\-125[0125]|windows\-874|iso\-8859\-[28])\?/i
> score CST_RUSSIANSPAM1 6.6
> describe CST_RUSSIANSPAM1 Russian SPAM, trap Subject line for
> language set
>
> header CST_RUSSIANSPAM2 From:raw =~
> /\=\?(koi8\-r|windows\-125[0125]|windows\-874|iso\-8859\-[28])\?/i
> score CST_RUSSIANSPAM2 6.6
> describe CST_RUSSIANSPAM2 Russian SPAM, trap From line for
> language set
I wonder why didn't you use the former? and also, why do you add score of
6.6 ?
> These two rules should tag your Cyrillic spam just fine. You might
> prefer to throw the language away entirely with the ok_languages etc.
> Just depends how you want to go about it.
the ok_* don't "throw anything entirely", they only score unwanted charsets
and languagees.
--
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Enter any 12-digit prime number to continue.
RE: Cyrillic spam
Posted by Michael Hutchinson <mh...@manux.co.nz>.
> -----Original Message-----
> From: Mike Pepe [mailto:lamune@doki-doki.net]
> Sent: Thursday, 20 March 2008 5:18 a.m.
> To: users@spamassassin.apache.org
> Subject: Cyrillic spam
>
> For some strange reason, I'm seeing Cyrillic spams very frequently
lately.
>
> None of my users read any Eastern European languages- is there a quick
> way to catch these?
>
> thanks
>
> -Mike
You could use the ok_languages and ok_locales settings. I'm sure
discussions on those can be found in the archives.
I employed these rules for my site:
header CST_RUSSIANSPAM1 Subject:raw =~
/\=\?(koi8\-r|windows\-125[0125]|windows\-874|iso\-8859\-[28])\?/i
score CST_RUSSIANSPAM1 6.6
describe CST_RUSSIANSPAM1 Russian SPAM, trap Subject line for
language set
header CST_RUSSIANSPAM2 From:raw =~
/\=\?(koi8\-r|windows\-125[0125]|windows\-874|iso\-8859\-[28])\?/i
score CST_RUSSIANSPAM2 6.6
describe CST_RUSSIANSPAM2 Russian SPAM, trap From line for
language set
These two rules should tag your Cyrillic spam just fine. You might
prefer to throw the language away entirely with the ok_languages etc.
Just depends how you want to go about it.
Cheers,
Mike