I am operating spamassassin in custom mode. Up till today I had TagLevel set at 6 and RejectLevel at 12, in order to complete the training.
Today I wanted to set the system in "operational" mode, that is simply delete anything that has a SA score of at least 6. For that purpose I set RejectLevel also at 6:
# config show spamassassin
spamassassin=service
DNSAvailable=yes
MessageRetentionTime=90
OkLanguages=en el
OkLocales=en el gr
RejectLevel=6
ReportSafe=0
Sensitivity=custom
SkipRBLChecks=0
SortSpam=enabled
Subject=[SPAM]
SubjectTag=enabled
TagLevel=6
TrustedNetworks=127/8 192.168/16
UseAutoWhitelist=0
UseBayes=1
status=enabled
However, /etc/mail/spamassassin/local.cf did not include this change, in fact there was no info on the reject level at all. Searching around in the templates, I came upon references in /etc/e-smith/templates/var/service/qpsmtpd/config/plugins/70spamassassin and /etc/e-smith/templates/var/service/qpsmtpd/config/peers/0/70spamassassin:
# cd /etc/e-smith/templates
# grep -R RejectLevel *
var/service/qpsmtpd/config/plugins/70spamassassin: if ($spamassassin{RejectLevel} > $spamassassin{TagLevel})
var/service/qpsmtpd/config/plugins/70spamassassin: push @options, "reject_threshold", $spamassassin{RejectLevel};
var/service/qpsmtpd/config/peers/0/70spamassassin: if ($spamassassin{RejectLevel} > $spamassassin{TagLevel})
var/service/qpsmtpd/config/peers/0/70spamassassin: push @options, "reject_threshold", $spamassassin{RejectLevel};
If I understand correctly, RejectLevel is inserted in the SA config files only if it is larger than TagLevel. But in this way, RejectLevel is effectively not used at all. Should perhaps ">" be ">=" or is would that break something else?
Bug or feature?
5 Replies
896 Views