Is the spamassassin Debian package unsafe to use in stable?
The issue is that things related to spam evolves rapidly, but
Debian stable is... stable.
El 9/6/25 a las 1:18, Vincent Lefevre escribi�:
Is the spamassassin Debian package unsafe to use in stable?
The issue is that things related to spam evolves rapidly, but
Debian stable is... stable.
Look at the version numbers:
spamassassin | 4.0.1-1~deb12u1 | stable | source, all spamassassin | 4.0.1-3 | testing | source, all spamassassin | 4.0.1-3 | unstable | source, all
At this moment, there is not a great difference between bookworm and trixie, as both are based on upstream version 4.0.1.
On Mon, Jun 09, 2025 at 01:18:37AM +0200, Vincent Lefevre wrote:
Is the spamassassin Debian package unsafe to use in stable?
I think so. I think the general expectation of spamassassin is that you
use a release for a long time.
Is the spamassassin Debian package unsafe to use in stable?
The issue is that things related to spam evolves rapidly, but
Debian stable is... stable.
its rules become obsolete, such as those that generate
RCVD_IN_VALIDITY_CERTIFIED_BLOCKED
RCVD_IN_VALIDITY_RPBL_BLOCKED
RCVD_IN_VALIDITY_SAFE_BLOCKED
while upstream gave them zero scores in May.
On Mon, Jun 09, 2025 at 08:03:58AM +0000, Andy Smith wrote:
On Mon, Jun 09, 2025 at 01:18:37AM +0200, Vincent Lefevre wrote:
Is the spamassassin Debian package unsafe to use in stable?
I think so. I think the general expectation of spamassassin is that you
use a release for a long time.
Oops! That was meant to read "I DON'T think so", as I hope the rest of
my email gave the hint.
sa-update already picked it up:
$ grep RCVD_IN_VALIDITY /var/lib/spamassassin/4.000001/updates_spamassassin_org/50_scores.cf
score RCVD_IN_VALIDITY_CERTIFIED 0
score RCVD_IN_VALIDITY_SAFE 0
score RCVD_IN_VALIDITY_RPBL 0
#score RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001
#score RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001
#score RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001
Jun 09 13:07:48 joooj spamd[164780]: check: dns_block_rule RCVD_IN_VALIDITY_RPBL_BLOCKED hit, creating /root/.spamassassin/dnsblock_bl.score.senderscore.com
Is the spamassassin Debian package unsafe to use in stable?
The issue is that things related to spam evolves rapidly, but
Debian stable is... stable.
So its rules become obsolete, such as
those that generate
RCVD_IN_VALIDITY_CERTIFIED_BLOCKED
RCVD_IN_VALIDITY_RPBL_BLOCKED
RCVD_IN_VALIDITY_SAFE_BLOCKED
while upstream gave them zero scores in May.
Rules are updated by the sa-update service, started e.g. by
| systemctl enable --now spamassassin-maintenance.timer
| systemctl start spamassassin-maintenance.service
Doing that, the scores are up to date:
| thh@angmar:~$ grep RCVD_IN_VALIDITY /var/lib/spamassassin/4.000001/updates_spamassassin_org/50_scores.cf
| score RCVD_IN_VALIDITY_CERTIFIED 0
| score RCVD_IN_VALIDITY_SAFE 0
| score RCVD_IN_VALIDITY_RPBL 0
| #score RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001
| #score RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001
| #score RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001
Vincent Lefevre (HE12025-06-09):
Jun 09 13:07:48 joooj spamd[164780]: check: dns_block_rule RCVD_IN_VALIDITY_RPBL_BLOCKED hit, creating /root/.spamassassin/dnsblock_bl.score.senderscore.com
A system service accessing files in the personal directory of root?
There is something seriously wrong here, but I cannot guess if it is in SpamAssassin's design or in the way it has been set up in this instance.
On 2025-06-09 16:24:41 +0200, Thomas Hochstein wrote:
| thh@angmar:~$ grep RCVD_IN_VALIDITY /var/lib/spamassassin/4.000001/updates_spamassassin_org/50_scores.cf
| score RCVD_IN_VALIDITY_CERTIFIED 0
| score RCVD_IN_VALIDITY_SAFE 0
| score RCVD_IN_VALIDITY_RPBL 0
| #score RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001
| #score RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001
| #score RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001
I have that, but this is ignored.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 40:36:50 |
| Calls: | 12,109 |
| Files: | 15,006 |
| Messages: | 6,518,399 |