Benjamin Adams wrote: > Think I found the problem just don't know how to fix: > running: spamassassin -D --lint 4261. > [9990] warn: config: warning: score set for non-existent rule BAYES_90
Looks like you've got an old local config trying over-ride the score for BAYES_90. However BAYES_90 no longer exists in SA 3.0.0 and higher, it was replaced by BAYES_95. > [9990] dbg: check: is spam? score=2.907 required=5 > [9990] dbg: check: > tests=BAYES_50,MISSING_SUBJECT,NO_REAL_NAME,NO_RECEIVED,NO_RELAYS,TO_CC_NONE > > [9990] dbg: check: > subtests=__HAS_MSGID,__MSGID_OK_DIGITS,__MSGID_OK_HOST,__NONEMPTY_BODY,__SANE_MSGID,__UNUSABLE_MSGID > > [9990] warn: lint: 1 issues detected, please rerun with debug enabled > for more information > > message in my inbox has: > X-Spam-Status: No, hits=0 tagged_above=-999 required=5 tests= > X-Spam-Level: > > Where can I get the score set for all BAYES? Well, you can get a list of all the bayes rules present in your current version of SA, and their default scores, by doing: grep "score BAYES_" /usr/share/spamassassin/50_scores.cf However, it looks like your configurations in /etc/mail/spamassassin or user_prefs are attempting to over-ride scores. So you'll have to check there for bayes declarations as well if you want to know what scores are being used. grep "BAYES_" /etc/mail/spamassassin/*.cf Note: Your system might use /usr/local/share instead of /usr/share, and might use /etc/spamassassin instead of /etc/mail/spamassassin. Substitute the appropriate directory names based on what's normal in your platform. Warning: Do not edit any files in /usr/share/spamassassin unless you know what you're doing. These files get deleted without warning when you upgrade.