Re: Suggestion to developers

2007-09-14 Thread Crocomoth
Matt Kettler-3 wrote: > > Sure, some messages will bail out faster, but most messages will take > much longer to scan. How is that better? > > I don't debate that the basic idea of having SA do this "automagically" > would be a great thing. However, the reality of doing it efficiently is > much

RE: Suggestion to developers

2007-09-13 Thread Michał Jęczalik
On Wed, 12 Sep 2007, Jason Burzenski wrote: How would you account for negative scoring rules? (if your message hit's score=5 it may soon be socre=-2 after a negative scoring rule is applied). It is stupid simple - run them first. :) -- Michał Jęczalik, +48.603.64.62.97 INFONAUTIC, +48.33.487.6

Re: Suggestion to developers

2007-09-13 Thread Bart Schaefer
On 9/13/07, Justin Mason <[EMAIL PROTECTED]> wrote: > > if anyone feels like trying it out to see if they can make an > auto-shortcircuiting plugin which outperforms base SpamAssassin over a > mixed corpus of 50:50 nonspam and spam, go for it ;) I dunno about your mail, but if it outperformed base

Re: Suggestion to developers

2007-09-13 Thread Justin Mason
Matt's generally nailed it. I would say that it should be easy enough to write a plugin which reorders rule priorities into a desired order, then implements the "have_shortcircuited" plugin hook to return 1 at the desired point... so if anyone feels like trying it out to see if they can make an a

Re: Suggestion to developers

2007-09-13 Thread Matt Kettler
Crocomoth wrote: > Matt Kettler-3 wrote: > >>> 1. Using this method, admin must understand that the fate of every >>> message >>> (for all users) will depend from the single rule. >>> >> Not if you set it up properly.. You can have multiple rules run with a >> very early priority (low nu

Re: Suggestion to developers

2007-09-13 Thread Crocomoth
Matt Kettler-3 wrote: > >> 1. Using this method, admin must understand that the fate of every >> message >> (for all users) will depend from the single rule. > Not if you set it up properly.. You can have multiple rules run with a > very early priority (low number), then have another one run wi

Re: Suggestion to developers

2007-09-13 Thread Matt Kettler
Crocomoth wrote: > Matt Kettler-3 wrote: > >> SA 3.2.x already does this, you just need to know how. Read the docs on >> the shortcircuit plugin, and the "priority" option for rules: >> >> Shortcircuit allows you to define when to "bail out" >> http://spamassassin.apache.org/full/3.2.x/doc/Mail_

Re: Suggestion to developers

2007-09-13 Thread Crocomoth
Matt Kettler-3 wrote: > > SA 3.2.x already does this, you just need to know how. Read the docs on > the shortcircuit plugin, and the "priority" option for rules: > > Shortcircuit allows you to define when to "bail out" > http://spamassassin.apache.org/full/3.2.x/doc/Mail_SpamAssassin_Plugin_Sho

Re: Suggestion to developers

2007-09-12 Thread Justin Mason
Henrik Krohns writes: > On Wed, Sep 12, 2007 at 08:53:10AM -0700, Crocomoth wrote: > > > The most effective way I've found to lower the SA footprint is to limit > > > the mail that gets to it by using some triage on the MTA side. SA as a > > > standalone tool might benefit from some kind of triag

RE: Suggestion to developers

2007-09-12 Thread Jason Burzenski
How would you account for negative scoring rules? (if your message hit's score=5 it may soon be socre=-2 after a negative scoring rule is applied). The most effective way I've found to lower the SA footprint is to limit the mail that gets to it by using some triage on the MTA side. SA as a stan

Re: Suggestion to developers

2007-09-12 Thread Matt Kettler
Crocomoth wrote: > SpamAssassin is a really great product. > But, it is perl-based and checks every message with a lot of (all) rules (, > always!). > Volume of spam is constantly increasing, as well as CPU and memory load that > SA creates on servers. > As a SA user, I would be happy to have the f

RE: Suggestion to developers

2007-09-12 Thread Crocomoth
> The most effective way I've found to lower the SA footprint is to limit > the mail that gets to it by using some triage on the MTA side. SA as a > standalone tool might benefit from some kind of triage functionality to > kill messages immediately as per a "blacklist" rule. The blacklist > ru

RE: Suggestion to developers

2007-09-12 Thread Crocomoth
Of course, this would not be simple to implement this, but, I think, as SA becomes more heavy, developers will be forced to find ways of "scissoring". To preserve nagative scores, SA could run these rules first. And, while sorting, SA should take into account possible dependencies between rules -

RE: Suggestion to developers

2007-09-12 Thread Skip Brott
In order to implement something like this, you would need to know the order of rules processing (which perhaps there is one - but I don't know it). You would need to be careful if you have rules which will assign negative scores which typically do so after other rules have already given positive o