On Thu, Oct 09, 2025 at 01:44:42PM -0400, Greg Troxel wrote: > > Yes they are set to zero, I use the standard settings on a Debian System > > You have miswrapped your grep output, too :-( > > > grep -nri "RCVD_IN_V" /usr/share/spamassassin/ > > /usr/share/spamassassin/50_scores.cf:287:score RCVD_IN_VALIDITY_RPBL 0 > > 1.284 0 1.310 # n=0 n=2 > > /usr/share/spamassassin/50_scores.cf:521:score RCVD_IN_VALIDITY_CERTIFIED > > 0.0 -3.0 0.0 -3.0 > > /usr/share/spamassassin/50_scores.cf:522:score RCVD_IN_VALIDITY_SAFE 0.0 > > -2.0 0.0 -2.0 > > So you seem not to have up-to-date rules.
That is wrong path (fallback path user in case your machine never has Internet connectivity so can't run sa-update). Debian auto-updated rules live in /var/lib/spamassassin, and values there those override those in /usr/share/spamassassin (just as those in /etc/spamassassin override both of them, and those in ~/.spamassassin override those too) E.g. something like this (with different SA version, depending on Debian version; this example is for oldoldstable AKA Bullseye to show which rules are set to zero even there): # egrep -r "^score.*RCVD_IN_V" /var/lib/spamassassin /var/lib/spamassassin/3.004006/updates_spamassassin_org/72_scores.cf:score RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 0.001 0.001 0.001 /var/lib/spamassassin/3.004006/updates_spamassassin_org/72_scores.cf:score RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 0.001 0.001 0.001 /var/lib/spamassassin/3.004006/updates_spamassassin_org/72_scores.cf:score RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 0.001 0.001 0.001 /var/lib/spamassassin/3.004006/updates_spamassassin_org/50_scores.cf:score RCVD_IN_VALIDITY_CERTIFIED 0 /var/lib/spamassassin/3.004006/updates_spamassassin_org/50_scores.cf:score RCVD_IN_VALIDITY_SAFE 0 /var/lib/spamassassin/3.004006/updates_spamassassin_org/50_scores.cf:score RCVD_IN_VALIDITY_RPBL 0 -- Opinions above are GNU-copylefted.
