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 triage functionality to > > > kill messages immediately as per a "blacklist" rule. The blacklist > > > rule(s) would be run against the messages before the normal ruleset was > > > applied. If any of the blacklist rules were triggered, the message > > > would be dropped without further scanning. > > > > I am not sure that messages after positive blacklist check will be dropped. > > As far as I see, SA just adds 100 points to this message and continues > > checking. > > And I am not sure about the order of rules in checking process. > > http://wiki.apache.org/spamassassin/ShortcircuitingRuleset
Yep, as Henrik notes, the shortcircuiting plugin implements this. We previously tried an automated method which rearranged the rule orderings automatically, and shortcircuited without any admin intervention -- but the automated approach just didn't work as well as the shortcircuit-plugin approach; it wound up slower overall, due to the overhead of frequent checking. --j.
