Benny Pedersen me at junc.org writes:
fuzzyocr stop scanning if spam score is over a limit, why scan
ocr when spamassassin can do it without ocr ?
Good to know.
it could maybe be a option to make spamassassin stop scanning in
generic if spam score is high ?
there is alot of plugins that
Matus UHLAR - fantomas uhlar at fantomas.sk writes:
You haven't read Matt's explanation of why it wasn't a good idea, did you?
There are rules with negative scores, which can puch the score back to the
ham, e.g. whitelist. Would you like to stop scoring before e.g. whitelist is
checked?
I
Matus UHLAR - fantomas uhlar at fantomas.sk writes:
That rises the question, whether the basic detections can be turned off.
I found the following options:
skip_rbl_checks 1
dns_available no
use_bayes 0
use_bayes_rules 0
bayes_auto_learn 0
- but I do not see an option
to turn
I would like to configure Spamassassin to only do certain tests
when the required_score is not yet reached.
For example, do the usual rule-based and bayesian tests first,
and if the score is lower than the required_score,
then do the DCC and RAZOR2 tests.
Is it possible?
Matt Kettler mkettler_sa at verizon.net writes:
In theory, a feature could be added to let you do something like this
(SA doesn't have this feature, but I'm proposing it could be added):
That would be a nice optimization: most of the spam we receive have a 10 score.
It seems a real waste of
ArtemGr artemciy at gmail.com writes:
I would like to configure Spamassassin to only do certain tests
when the required_score is not yet reached.
For example, do the usual rule-based and bayesian tests first,
and if the score is lower than the required_score,
then do the DCC and RAZOR2 tests
