I ran some updates last week and mail is no longer coming in or going out. From the bounce message (below) which was received by an external sender attempting to mail someone on the Virtualmin box, it looks like mail is trying to listen on port 10024, which is an Amavisd port, according to google. Apparently this got installed during a virtualmin update. Any suggestions on how to troubleshoot? Postfix is running, I can telnet to the server on port 25 and I have port 10024 open on the firewall, and I have disabled both Spamassassin and ClamAV (for now).
This is the mail system at host reaver.xxx.com.
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
The mail system
email@example.com: delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Amavis isn't something Virtualmin uses or installs... that would only be put onto your system if the sysadmin manually installed it, or, if a package the sysadmin installed pulled it in.
The key would be to either fix Amavis, or, remove it from the configuration.
Thanks Eric, I would be the sysadmin. I ran the updates from within Virtualmin (the package updates). Those are the only ones. I'm not familiar with Amavis at all, but will look into a manual uninstall.
Well this is odd. Apparently Amavis is not / was not installed. So why is the mail server sending that original rejection message for port 10024?
[root@zoe etc]# which amavis /usr/bin/which: no amavis in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin) [root@zoe etc]# which amavisd /usr/bin/which: no amavisd in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin) [root@zoe etc]#