• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

qmail not using spamassassin

K

kerm1t

Guest
SpamAssassin is enabled and configured in Plesk, but none of my incoming mail is being scanned (no X-SpamAssassin headers).

It doesn't appear as if qmail has been configured to use SpamAssassin. spamd is running, but the maillog doesn't show qmail calling it. I'm familiar with the qmail-queue-scan.pl method of integrating SA, but perhaps are there other methods too/

I guess I'll end up installling qmail-queue-scan.pl myself; I'm just rather suprised that Plesk offers SA in the control panel, but then doesn't integrate it into the MTA. Is this a glaring oversight by swsoft, or something perculiar about my system (Plesk 7.5.4 on FC3)?
 
I would recommend that you check out using qmail-scanner from the atomicrocketturtle.com yum repo. It will integrate/control your antivirus, spamassassin, and qmail quite nicely.

May not play well with the psa-spamassassin GUI interface module, but you will get much better control/protection with q-s. The downside is that there is no GUI for it, manual edit / configuration. Works with many AV packages, not DrWeb
 
Cheers for the reply; I've found the problem now though.

SA is integrated via .qmail file in /var/mailnames/domain/user/. The shell script in this file was attempting to connect to spamd via a non-existant socket. Creating a sym link fixed the problem.
 
Back
Top