1 Topic by rkio (edited by rkio 2024-09-11 01:55:47)

  • rkio
  • Member
  • Offline
  • Registered: 2021-05-15
  • Posts: 5

Topic: Why does the SpamAssassin kill threshold not reflect what's configured

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):
- Deployed with iRedMail Easy or the downloadable installer?
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Running iRedMail-1.7.0 on Rocky 9.4, MySQL backend, Nginx, iRedAdmin-Pro-SQL-5.6

Even though we have the Spam Global Policy set to 4.0 (for both Mark as Spam and block & quarantine score) nearly all the emails quarantined are coming up with X-SPAM-STATUS showing kill=0. Why may this be occurring?

Here is an excerpt of the X-SPAM-Status headers from a quarantined email:

---------
Yes, score=0.476 tag=0 tag2=0 kill=0 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LOTS_OF_MONEY=0.001, MONEY_NOHTML=0.669, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
-------

Thank you

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by rkio

  • rkio
  • Member
  • Offline
  • Registered: 2021-05-15
  • Posts: 5

Re: Why does the SpamAssassin kill threshold not reflect what's configured

I found the following post describing the exact same issue:

https://forum.iredmail.org/topic20355-b … -spam.html

I confirmed that by clearing the global spam policy kill threshold in iredadmin-pro to default that amavisd/spamassassin then correctly uses kill=6.9 when processing emails.

Once you set the global spam policy kill threshold in iredadmin-pro to anything other than the default, this somehow breaks amavisd/spamassassin's ability to retrieve the correct spam_kill_threshold.

NOTE: I confirmed that the policy table in the amavisd database is updated as expected when you set the global spam policy kill threshold in ireadmin-pro to anything other than default, but somehow amavisd/spamassassin stil falls back to kill=0 when an email is processed thru postfix