You can test to see what ports are in a listening state and what processes, applications, or daemons are listening by running: When I did that, I noticed that amavisd wasn’t listening on port 10024, which made me think that it wasn’t running at all.
That’s when I ran into the strange part of the problem: the init script output: So, apparently it is running and not running at the same time (sounds like a Linux version of Schrödinger’s cat to me)!
After applying the updates, and restarting the necessary components of the mail stack, I ran my usual test of sending an email from one of my accounts to another one. However, I realised that it isn’t a completely valid test to send an email from one internal account to another because I have amavisd configured to not scan anything coming from my trusted IPs and domains.
I noticed several hundred mails in the queue when I ran That indicated to me that it wasn’t a problem with Postfix (and I knew it wasn’t a problem with Dovecot, because I could connect to my accounts via IMAP).
Amavisd-new is a content filtering framework utilizing helper applications for virus filtering and spam filtering.
In this setup we will be using two helper applications one Clam AV for filtering virus mails and Spamassassin for filtering spam.
Seeing as amavisd is running on localhost:10024, I figured that that is where the problem had to be.
invoke-rc.d: initscript amavis, action "start" failed. amavis.service - LSB: Starts amavisd-new mailfilter Loaded: loaded (/etc/init.d/amavis; generated; vendor preset: enabled Active: failed (Result: exit-code) since Mon 2016-11-14 IST; 9ms ago Docs: man:systemd-sysv-generator(8) Process: 5465 Exec Start=/etc/init.d/amavis start (code=exited, status=1/FAILURE) Nov 14 lenovo amavis: The value of variable $myhostname is..Nov 14 lenovo amavis: a fully qualified domain name; perha...h.
It was obvious, though, that it wasn’t actually running (which could be verified with ‘ps -elf | grep -i amavis’). I tried manually removing the PID file, but that actually just made matters a bit worse.
Ultimately, this combination is what fixed the problem for me: It seems that the Spam Assassin rules file had gone missing, and that was causing amavisd to not start properly.
Spamassassin itself can function as yet another layer of content filtering framework and utilize the helper applications Vipul's Razor2 and DCC.
Unlike many other spam fighting technologies like RBLs and others Spamassassin does not simply accept or reject a given email based on one single test.