|Main Archive Page > Month Archives > spamassassin-users archives|
btw, I think this is already possible using the shortcircuit plugin.
Just use rule priorities to run the non-net rules first, and
shortcircuit if they are sufficient.
On Sat, Oct 30, 2010 at 08:05, Henrik K <firstname.lastname@example.org> wrote:
> On Sat, Oct 30, 2010 at 02:23:00AM -0400, Darxus@ChaosReigns.com wrote:
>> On 10/30, Michael Parker wrote:
>> > > I'd like to see spamassassin only run network tests when they might
>> > > affect the outcome.
>> > Why?
>> To reduce the network load on my server which is one of the hosts of the
>> DNSWL.org list?
>> > Assuming a reasonably fast connection network checks are basically free.
>> That seems weird.
>> But the total amount of bandwidth and processing time saved on the
>> internet from not running unnecessary tests on every instance of
>> spamassassin seems worth doing.
>> Why not?
> It's nice that you are requesting a feature without any single proof that it
> would be generally useful. It would only make things in all ways much more
> complex, create additional delays, hinder log analyzing etc. What if there
> are lots of metas involving DNS rules or shortcircuits etc? It would become
> a big mess.
> This is just a different variation of the age old question that pops up here
> now and then. No one has yet showed it would have enough merits to