Hello everybody,
I'm new to the list so please excuse me if this topic was beaten to death...
I'm very impressed with spam assassin acuracy in spam detection, however
it is not as fast as I wish it was (which is very much understandable given
that spamassassin is written in perl and uses huge number of regex tests).
PerMsgStatus runs
<quote>
#... ALL the tests, even if a spam triggers lots of them early on.
# this lets us see ludicrously spammish mails (score: 40) etc., which
# we can then immediately submit to spamblocking services.
</quote>
The question is: why do I need to run all tests if I'm running spamassassin with -L
flag?
I suggest adding another flag to spamassassin to make PerMsgStatus return as soon as
hit count reaches required_hits level. This flag would imply -L flag as well.
I added
last TEST if($self->{hits} >= $self->{conf}->{required_hits});
to check sub in PerMsgStatus.pm after every test performed in order to see
what kind of performance gain I will get.
I performed benchmarks on 300+ spam/nonspam messages from my mailbox.
I started 30 simultaneous scans (about 10 msg per), and found
that on average I get 22-24% improvement in time taken to scan these messages.
I really think that this would be a reasonable option to have.
Again, sorry if this topic was beaten to death before...
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
