On Oct 29, 2010, at 8:42 PM, dar...@chaosreigns.com wrote:
> I'd like to see spamassassin only run network tests when they might
> affect the outcome.
Why?
Assuming a reasonably fast connection network checks are basically free.
They are kicked off at the start of a scan and the results are compared at the
end. You're not exactly waiting on network tests to run since all the other
rules are run in the mean time.
>
> For example, if you run all non-network tests, and at that point an email's
> score qualifies as spam, and then you run all the non-spam network tests
> (hitting whitelists), and it still qualifies as spam, there's no reason
> to ever run the spam network tests (hitting blacklists).
>
> Right?
>
> Perl pseudocode:
>
> run_non_network_tests();
> NETTEST: while (1) {
> if ($score < 5) {
> run_one_network_spam_test() or last NETTEST;
> } else {
> run_one_network_nonspam_test() or last NETTEST;
> }
> }
>
Ok, lets assume that this actually buys you something. Good thing that you can
provide your own Check.pm. You can easily provide your own.
Michael
>
> Of course it would be necessary to have an option to disable this, for
> things like submitting corpora to the mass checks.
>
> I would probably run the network tests in random order. But I might have
> more affinity for randomness than average.
>
> --
> "Let's just say that if complete and utter chaos was lightning, then
> he'd be the sort to stand on a hilltop in a thunderstorm wearing wet
> copper armour and shouting 'All gods are bastards'." - The Color of Magic
> http://www.ChaosReigns.com
