Re: Suggestion to developers

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 following possibility in the next
> version:
> 1. Add an option which will allow to limit number of rules run against every
> message. I.e., if the limit of spam points is reached to required_score,
> stop further checking and process the message as a spam.
> I think, not all users really interested in gathering all statistics about
> all spam messages.
> 2. According to (1), it makes sense to sort all rules from lightweight to
> heavyweight (including ones which require internet queries) and make
> checking in this order.
>
> This could allow to lower SA footprint.
>

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_Shortcircuit.html

And priority, documented in the "Rule definitions and privileged settings" section of the Conf manpage, allows you to tell SA what order to run rules in.

http://spamassassin.apache.org/full/3.2.x/doc/Mail_SpamAssassin_Conf.html#rule_definitions_and_privileged_settings

Note however that over-using priority on the rules can be detrimental to your performance, forcing SA to scan through the message many times.

>
Received on Wed Sep 12 18:49:13 2007