I followed this guide: https://www.howtoforge.com/perfect-...3#-install-amavisdnew-spamassassin-and-clamav on a Centos 7.4 server. Mail can't be received. Amavisd.service fails to start Code: amavisd.service - Amavisd-new is an interface between MTA and content checkers. Loaded: loaded (/usr/lib/systemd/system/amavisd.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Sun 2018-01-14 13:51:31 EST; 11s ago Docs: http://www.ijs.si/software/amavisd/#doc Process: 27218 ExecStart=/usr/sbin/amavisd -c /etc/amavisd/amavisd.conf (code=exited, status=13) Jan 14 13:51:31 host.xxxxx.net systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers.. Jan 14 13:51:31 host.xxxxx.net systemd[1]: Unit amavisd.service entered failed state. Jan 14 13:51:31 host.xxxxx.net systemd[1]: amavisd.service failed. Jan 14 13:51:31 host.xxxxx.net systemd[1]: amavisd.service holdoff time over, scheduling restart. Jan 14 13:51:31 host.xxxxx.net systemd[1]: start request repeated too quickly for amavisd.service Jan 14 13:51:31 host.xxxxx.net systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers.. Jan 14 13:51:31 host.xxxxx.net systemd[1]: Unit amavisd.service entered failed state. Jan 14 13:51:31 host.xxxxx.net systemd[1]: amavisd.service failed.
Try to restart it. If it does not start, then take a look in the maillog to see why it fails. Common errors are wrong (non fqdn) hostnames.
This 'cat /var/log/maillog | grep 'amavisd'' gave me this: Code: Jan 15 00:51:38 host amavis[2906]: (02906-01) (!)connect to /var/run/clamd.amavisd/clamd.sock failed, attempt #1: Can't connect to a UNIX socket /var/run/clamd.amavisd/clamd.sock: No such file or directory Jan 15 00:51:38 host amavis[2905]: (02905-01) (!)connect to /var/run/clamd.amavisd/clamd.sock failed, attempt #1: Can't connect to a UNIX socket /var/run/clamd.amavisd/clamd.sock: No such file or directory Jan 15 00:51:39 host amavis[2905]: (02905-01) (!)connect to /var/run/clamd.amavisd/clamd.sock failed, attempt #1: Can't connect to a UNIX socket /var/run/clamd.amavisd/clamd.sock: No such file or directory Jan 15 00:51:39 host amavis[2906]: (02906-01) (!)connect to /var/run/clamd.amavisd/clamd.sock failed, attempt #1: Can't connect to a UNIX socket /var/run/clamd.amavisd/clamd.sock: No such file or directory Jan 15 00:51:39 host amavis[2905]: (02905-01) (!)ClamAV-clamd: All attempts (1) failed connecting to /var/run/clamd.amavisd/clamd.sock, retrying (2) Jan 15 00:51:39 host amavis[2906]: (02906-01) (!)ClamAV-clamd: All attempts (1) failed connecting to /var/run/clamd.amavisd/clamd.sock, retrying (2) Jan 15 00:51:45 host amavis[2905]: (02905-01) (!)connect to /var/run/clamd.amavisd/clamd.sock failed, attempt #1: Can't connect to a UNIX socket /var/run/clamd.amavisd/clamd.sock: No such file or directory Jan 15 00:51:45 host amavis[2906]: (02906-01) (!)connect to /var/run/clamd.amavisd/clamd.sock failed, attempt #1: Can't connect to a UNIX socket /var/run/clamd.amavisd/clamd.sock: No such file or directory Jan 15 00:51:45 host amavis[2906]: (02906-01) (!)ClamAV-clamd av-scanner FAILED: run_av error: Too many retries to talk to /var/run/clamd.amavisd/clamd.sock (All attempts (1) failed connecting to /var/run/clamd.amavisd/clamd.sock) at (eval 134) line 659.\n Jan 15 00:51:45 host amavis[2905]: (02905-01) (!)ClamAV-clamd av-scanner FAILED: run_av error: Too many retries to talk to /var/run/clamd.amavisd/clamd.sock (All attempts (1) failed connecting to /var/run/clamd.amavisd/clamd.sock) at (eval 134) line 659.\n I can confirm the file is there and it exists. I don't understand why it can't find it. If I run Amavisd as root it works just fine.