You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Julian Yap <ju...@gmail.com> on 2010/03/09 22:56:56 UTC
Re: Low scores
Just wanted to add that this particular line is incorrect:
meta SC_HAM (USER_IN_WHITELIST||USER_IN_DEF_WHITELIST||
USER_IN_ALL_SPAM_TO||NO_RELAYS||ALL_TRUSTED||USER_IN_BLACKLIST_TO||
USER_IN_BLACKLIST)
That will have Blacklisted email filters classified as ham.
- Julian
On Sun, Feb 24, 2008 at 8:07 AM, Micah Anderson <mi...@riseup.net> wrote:
> On Sun, 24 Feb 2008 02:15:24 +0100, Matthias Leisi wrote:
>
> > Micah Anderson schrieb:
> >
> > | [surprisingly low scores]
> > | The spams can be pulled from here: http://micah.riseup.net/spams
> >
> > Most (all?) of the samples are forwarded through some debian.org
> > mechanism. In order for blacklists to take full effect, you should
> > configure your trust path (trusted_networks etc) accordingly.
>
> My trusted_networks is set to:
>
> trusted_networks 202.12.162.
> trusted_networks 10.0.
> trusted_networks 10.8.0.
>
> The first is trusting everything in that IP space, which we control, the
> second is a private network, and the third is a private network. Am I
> specifying those incorrectly perhaps?
>
> I'm also short-circuiting on trusted-relay chained messages, using the
> following:
>
> meta SC_HAM (USER_IN_WHITELIST||USER_IN_DEF_WHITELIST||
> USER_IN_ALL_SPAM_TO||NO_RELAYS||ALL_TRUSTED||USER_IN_BLACKLIST_TO||
> USER_IN_BLACKLIST)
> priority SC_HAM -1000
> shortcircuit SC_HAM ham
> score SC_HAM -20
>
> But I log in the headers all short-circuit status, with the following
> (and you wont see short-circuiting in the examples i posted):
>
> status
> add_header all Status "_YESNO_, score=_SCORE_ required=_REQD_
> tests=_TESTS_ shortcircuit=_SCTYPE_ autolearn=_AUTOLEARN_
> version=_VERSION_"
>
> Do I have something misconfigured in my trust path? I do have a forward
> from a debian.org email address that occasionally sends me legit email
> (although it does seem like a lot of spam gets through there), but I dont
> believe I have that domain in a whitelist anywhere.
>
> thanks
> micah
>
>
Re: Low scores
Posted by micah anderson <mi...@riseup.net>.
On Fri, 12 Mar 2010 15:44:21 -1000, Julian Yap <ju...@gmail.com> wrote:
> On Thu, Mar 11, 2010 at 7:58 AM, micah anderson <mi...@riseup.net> wrote:
>
> > On Tue, 9 Mar 2010 11:56:56 -1000, Julian Yap <ju...@gmail.com>
> > wrote:
> > > Just wanted to add that this particular line is incorrect:
> > > meta SC_HAM (USER_IN_WHITELIST||USER_IN_DEF_WHITELIST||
> > > USER_IN_ALL_SPAM_TO||NO_RELAYS||ALL_TRUSTED||USER_IN_BLACKLIST_TO||
> > > USER_IN_BLACKLIST)
> > >
> > > That will have Blacklisted email filters classified as ham.
> >
> > Interesting, thanks for the reply from an old thread.
> >
> > I got this list from:
> > http://wiki.apache.org/spamassassin/ShortcircuitingRuleset which seems
> > to be something that Justin Mason put together. I have CC'd Justin on
> > this email.
> > Which has the difference of also including "SUBJECT_IN_WHITELIST", and
> > "SUBJECT_IN_BLACKLIST"... but now I am wondering if this is the right
> > thing to do.
I actually removed the SUBJECT_IN rules as this makes it so any
individual user who can whitelist/blacklist a subject can shortcircuit
for everyone.
> > I'm very curious about resolving this, it does seem like a bad setup and
> > it is being taken as gospel from the spamassassin wiki, but perhaps
> > there is something that we are not understanding here that Justin can
> > clarify?
> >
>
> I'm pretty sure yours is wrong. You need to take out the the rules which
> apply to Spam in spam short circuiting.
I agree with you, its amazing that this has been wrong on the wiki since
2007! I went to go update the wiki today, and found that you had just
done it. Thanks for doing that!
Micah
Re: Low scores
Posted by Julian Yap <ju...@gmail.com>.
On Fri, Mar 12, 2010 at 3:44 PM, Julian Yap <ju...@gmail.com> wrote:
> On Thu, Mar 11, 2010 at 7:58 AM, micah anderson <mi...@riseup.net> wrote:
>
>> On Tue, 9 Mar 2010 11:56:56 -1000, Julian Yap <ju...@gmail.com>
>> wrote:
>> > Just wanted to add that this particular line is incorrect:
>> > meta SC_HAM (USER_IN_WHITELIST||USER_IN_DEF_WHITELIST||
>> > USER_IN_ALL_SPAM_TO||NO_RELAYS||ALL_TRUSTED||USER_IN_BLACKLIST_TO||
>> > USER_IN_BLACKLIST)
>> >
>> > That will have Blacklisted email filters classified as ham.
>>
>> Interesting, thanks for the reply from an old thread.
>>
>> I got this list from:
>> http://wiki.apache.org/spamassassin/ShortcircuitingRuleset which seems
>> to be something that Justin Mason put together. I have CC'd Justin on
>> this email.
>>
>> This list specifies that this was a good shortcircuit rule to have first
>> because these are non-network-based whitelists, locally-generated
>> messages, messages via a trusted relay chain, simple non-network based
>> blacklists.
>>
>> Mine now reads:
>>
>> meta SC_HAM
>> (USER_IN_WHITELIST||USER_IN_DEF_WHITELIST||USER_IN_ALL_SPAM_TO||SUBJECT_IN_WHITELIST||NO_RELAYS||ALL_TRUSTED||USER_IN_BLACKLIST_TO||USER_IN_BLACKLIST||SUBJECT_IN_BLACKLIST)
>> priority SC_HAM -1000
>> shortcircuit SC_HAM ham
>> score SC_HAM -20
>>
>> Which has the difference of also including "SUBJECT_IN_WHITELIST", and
>> "SUBJECT_IN_BLACKLIST"... but now I am wondering if this is the right
>> thing to do.
>>
>> I'm very curious about resolving this, it does seem like a bad setup and
>> it is being taken as gospel from the spamassassin wiki, but perhaps
>> there is something that we are not understanding here that Justin can
>> clarify?
>>
>
> I'm pretty sure yours is wrong. You need to take out the the rules which
> apply to Spam in spam short circuiting.
>
> Here's what I have for my 'ham' section:
> meta SC_HAM (USER_IN_WHITELIST||USER_IN_ALL_SPAM_TO||ALL_TRUSTED)
>
> priority SC_HAM -1000
> shortcircuit SC_HAM ham
> score SC_HAM -1
>
> Here is my 'spam' section:
> meta SC_SPAM (USER_IN_BLACKLIST_TO||USER_IN_BLACKLIST)
> priority SC_SPAM -950
> shortcircuit SC_SPAM spam
> score SC_SPAM 1
>
As an update to this, I rewrote the rules section of this Wiki page:
http://wiki.apache.org/spamassassin/ShortcircuitingRuleset
- Julian
Re: Low scores
Posted by Julian Yap <ju...@gmail.com>.
On Thu, Mar 11, 2010 at 7:58 AM, micah anderson <mi...@riseup.net> wrote:
> On Tue, 9 Mar 2010 11:56:56 -1000, Julian Yap <ju...@gmail.com>
> wrote:
> > Just wanted to add that this particular line is incorrect:
> > meta SC_HAM (USER_IN_WHITELIST||USER_IN_DEF_WHITELIST||
> > USER_IN_ALL_SPAM_TO||NO_RELAYS||ALL_TRUSTED||USER_IN_BLACKLIST_TO||
> > USER_IN_BLACKLIST)
> >
> > That will have Blacklisted email filters classified as ham.
>
> Interesting, thanks for the reply from an old thread.
>
> I got this list from:
> http://wiki.apache.org/spamassassin/ShortcircuitingRuleset which seems
> to be something that Justin Mason put together. I have CC'd Justin on
> this email.
>
> This list specifies that this was a good shortcircuit rule to have first
> because these are non-network-based whitelists, locally-generated
> messages, messages via a trusted relay chain, simple non-network based
> blacklists.
>
> Mine now reads:
>
> meta SC_HAM
> (USER_IN_WHITELIST||USER_IN_DEF_WHITELIST||USER_IN_ALL_SPAM_TO||SUBJECT_IN_WHITELIST||NO_RELAYS||ALL_TRUSTED||USER_IN_BLACKLIST_TO||USER_IN_BLACKLIST||SUBJECT_IN_BLACKLIST)
> priority SC_HAM -1000
> shortcircuit SC_HAM ham
> score SC_HAM -20
>
> Which has the difference of also including "SUBJECT_IN_WHITELIST", and
> "SUBJECT_IN_BLACKLIST"... but now I am wondering if this is the right
> thing to do.
>
> I'm very curious about resolving this, it does seem like a bad setup and
> it is being taken as gospel from the spamassassin wiki, but perhaps
> there is something that we are not understanding here that Justin can
> clarify?
>
I'm pretty sure yours is wrong. You need to take out the the rules which
apply to Spam in spam short circuiting.
Here's what I have for my 'ham' section:
meta SC_HAM (USER_IN_WHITELIST||USER_IN_ALL_SPAM_TO||ALL_TRUSTED)
priority SC_HAM -1000
shortcircuit SC_HAM ham
score SC_HAM -1
Here is my 'spam' section:
meta SC_SPAM (USER_IN_BLACKLIST_TO||USER_IN_BLACKLIST)
priority SC_SPAM -950
shortcircuit SC_SPAM spam
score SC_SPAM 1
- Julian
Re: Low scores
Posted by micah anderson <mi...@riseup.net>.
On Tue, 9 Mar 2010 11:56:56 -1000, Julian Yap <ju...@gmail.com> wrote:
> Just wanted to add that this particular line is incorrect:
> meta SC_HAM (USER_IN_WHITELIST||USER_IN_DEF_WHITELIST||
> USER_IN_ALL_SPAM_TO||NO_RELAYS||ALL_TRUSTED||USER_IN_BLACKLIST_TO||
> USER_IN_BLACKLIST)
>
> That will have Blacklisted email filters classified as ham.
Interesting, thanks for the reply from an old thread.
I got this list from:
http://wiki.apache.org/spamassassin/ShortcircuitingRuleset which seems
to be something that Justin Mason put together. I have CC'd Justin on
this email.
This list specifies that this was a good shortcircuit rule to have first
because these are non-network-based whitelists, locally-generated
messages, messages via a trusted relay chain, simple non-network based
blacklists.
Mine now reads:
meta SC_HAM (USER_IN_WHITELIST||USER_IN_DEF_WHITELIST||USER_IN_ALL_SPAM_TO||SUBJECT_IN_WHITELIST||NO_RELAYS||ALL_TRUSTED||USER_IN_BLACKLIST_TO||USER_IN_BLACKLIST||SUBJECT_IN_BLACKLIST)
priority SC_HAM -1000
shortcircuit SC_HAM ham
score SC_HAM -20
Which has the difference of also including "SUBJECT_IN_WHITELIST", and
"SUBJECT_IN_BLACKLIST"... but now I am wondering if this is the right
thing to do.
I'm very curious about resolving this, it does seem like a bad setup and
it is being taken as gospel from the spamassassin wiki, but perhaps
there is something that we are not understanding here that Justin can
clarify?
micah