The SpamAssassin service is always stopped when the Warden Anti-spam and Virus Protection extension is installed.

The SpamAssassin service is always stopped when the Warden Anti-spam and Virus Protection extension is installed:

# systemctl status spamassassin
● spamassassin.service
   Loaded: masked (Reason: Unit spamassassin.service is masked.)
   Active: inactive (dead)

Warden disables the SpamAssassin service because Amavis executes SpamAssassin subroutines directly, so it is expected that there is no separate process for SpamAssassin. Because of this leaving the SpamAssassin service running would be a waste of memory and server resources. You should not try to enable it.

  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

How can I fix any statistics generation problems?

Missing the Warden Crontab Entry There is a crontab entry that will update Warden statistics...

How can I fix the error: "milter-reject: END-OF-MESSAGE from..." in the log and found the AV in error (cannot read /etc/clam.d/scan.conf).

Cloudlinux / Imunify360 added their own version of ClamAV to their repo which accidentally...

How can I fix the error: Can't connect to TCP port 10024 on ::1 [Cannot assign requested address] when trying to start Amavis?

When trying to start Amavis you see this in the mail log: Oct 02 03:20:15 condor3648 systemd[1]:...

How can I fix the error: Error [Contentfilter_Settings_Contentfilter]. Message [[QUARANTINEDIR] must be a valid directory?

This error means that Amavis was not installed correctly. Try running the Warden from the command...

How can I fix the error: host 127.0.0.1[127.0.0.1] said: 552 5.3.4 Declared message size (1208029 B) exceeds size limit for recipient?

You can set the message size limit for Amavis under Settings -> Policy Settings -> Misc...