On 2026-04-09 19:36:51 +0200, Matus UHLAR - fantomas wrote: > > > On 09.04.26 15:16, Vincent Lefevre wrote: > > > > They were supposed to be disabled by default. Has this changed? > > > On 2026-04-09 17:30:50 +0200, Matus UHLAR - fantomas wrote: > > > no, although it was never fully implemented because these were forgotten > > > somehow: > > > > > > 72_scores.cf:score RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 0.001 > > > 0.001 0.001 > > > 72_scores.cf:score RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 0.001 > > > 0.001 0.001 > > > 72_scores.cf:score RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 0.001 > > > 0.001 0.001 > > On 09.04.26 18:38, Vincent Lefevre wrote: > > In any case, I don't understand why I get the score 1 with these lines. > > Do you have those? > > Don't you have overrides anywhere?
I think I've found the cause: /var/lib/spamassassin just contains drwxr-xr-x 3 debian-spamd debian-spamd 4096 2025-06-22 18:14:17 4.000001/ drwxr-xr-x 3 debian-spamd debian-spamd 4096 2026-02-28 11:59:53 compiled/ drwx------ 3 debian-spamd debian-spamd 4096 2026-02-28 11:59:47 sa-update-keys/ where the above lines are somewhere under 4.000001 while SpamAssassin is now 4.0.2 (but no 4.000002 directory!). In my logs, I can see 2025-06-22T18:14:15+02:00 qaa systemd[1]: Starting spamassassin-maintenance.service - Daily spamassassin rule refresh... and this is the only instance of "spamassassin-maintenance.service". Indeed, this was a test for some bug in spamd: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108166#22 (which I posted 3 minutes later, on 2025-06-22 18:17:17). The fact that 4.000001 is still there and the only such directory was misleading (obviously I had not remembered the above test until now). I've now done systemctl enable --now spamassassin-maintenance.timer which should solve the issue in a few hours. -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
