Blacklisting efficiently using "first and final" rules?

[Kelly Jones <ke...@gmail.com>]

Blacklisting with SpamAssassin is easy: just add a rule with a high score.

However, this seems inefficient, since SpamAssassin will still go
through its entire ruleset to calculate a score.

Is it possible to setup "first and final" rules in SpamAssassin. That
is, rules that are: 1) checked before any other rules, and 2) if any
of the rules are hit, no other rules are checked.

Given that some tests (especially network-based tests?) are expensive
and that most people get a lot of spam, I think this would help a lot,
but I could be wrong: any thoughts on whether this would really
increase efficiency?

Of course, "first and final" rules could be used for whitelisting, too.

-- 
We're just a Bunch Of Regular Guys, a collective group that's trying
to understand and assimilate technology. We feel that resistance to
new ideas and technology is unwise and ultimately futile.

Re: Blacklisting efficiently using "first and final" rules?

[Theo Van Dinter <fe...@apache.org>]

On Wed, Jan 17, 2007 at 09:34:10AM -0500, Theo Van Dinter wrote:
> > Is it possible to setup "first and final" rules in SpamAssassin. That
> > is, rules that are: 1) checked before any other rules, and 2) if any
> > of the rules are hit, no other rules are checked.
> 
> 1) Absolutely, see "priority" in the docs.
> 2) Not with the currently released code.  3.2 will have short-circuit
>    functionality to do this..

3) the best way to accomplish this (even w/ 3.2) is to not send mails that
   you want to whitelist/blacklist into SpamAssassin at all.  do the decision
   outside of SA and don't call it for mails that meet your criteria.

-- 
Randomly Selected Tagline:
For Sale: Dehydrated H2O - $14 per quart

Re: Blacklisting efficiently using "first and final" rules?

[Theo Van Dinter <fe...@apache.org>]

On Wed, Jan 17, 2007 at 07:25:24AM -0700, Kelly Jones wrote:
> Is it possible to setup "first and final" rules in SpamAssassin. That
> is, rules that are: 1) checked before any other rules, and 2) if any
> of the rules are hit, no other rules are checked.

1) Absolutely, see "priority" in the docs.
2) Not with the currently released code.  3.2 will have short-circuit
   functionality to do this..

-- 
Randomly Selected Tagline:
He has his own unique version of the English language...