Previous to the last updates I was receiving mail correctly. I do not, and have not, modified any of the configuration files involved in the mail delivery.
Pointing me at a thread that implies amavisd is not running does not help, as my post clearly shows that port 10024 is in listening mode.
Perhaps the update did.[quote=“EddieA, post:3, topic:7295”]
Pointing me at a thread that implies amavisd is not running does not help
[/quote]
Did you read this?
Have the same issue:
Dec 19 15:23:56 sd postfix/smtp[179]: BFE3738054E: to=the@mail.com, relay=none, delay=0.14, delays=0.13/0.01/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
>postfix and amavisd-new are started.
>Restart amavisd and if it does not start, check the mail.log file for the reason.
>I did this earlier:
In /etc/clamav/clamd.conf
AllowSupplementaryGroups false -> true
But then I didn't restart it...
So:
service clamav-daemon restart
Solved the issue.
PS: I only tried to help, it’s not my area of expertise.
Please confirm that amavisd is working on port 10024 with the following command:
$ nc localhost 10024
220 [127.0.0.1] ESMTP amavisd-new service ready
If it doesn’t, try to restart the service (through server-manager or systemctl restart amavisd
If the restart fixes, please search /var/log/maillog for amavisd restarts in the past (maybe close in time to the update).
Let us know, please.
So, what it looks like happened was that after the re-boot for the previous updates, amavisd started on the IPv6 listener instead of the IPv4. The restart I did mid re-boots, based on the earlier replies, correctly, started it on the IPv4 which made everything work fine.
Wonder why the previous re-boot picked the wrong protocol.
amavisd has been recently updated to run better under systemd (which is our/centos7 case).
I don’t know if it may have solved this issue.
I see After=network.target
in amavisd systemd startup script.