I have just set up a new Axigen server to replace my iReadMail server. DNS is set up with A, MX, DMARC, DKIM, and SPF records. Reverse DNS is also setup. I am running the mail server on a VPS with an IP address and domain that are not blacklisted.
When I send mail to my old server it works great. But when I send mail to Gmail and Outlook the mail is not delivered.
Outlook.com error
4.7.0 Timeout waiting for client input
Please increase the log level to Protocol Communication level for SMTP Sending service and share the SMTP-OUT log lines related to a fresh new message sent to a Gmail recipient.
Also please let us know the Axigen version you are currently using.
I installed a plain Ubuntu mail server VM on that IP and it sent mail to gMail and Outlook.live.com without a problem. Even though the new DKIM signature in DNS had not propagated yet.
The Axigen mail server that is not working was installed following the online instructions and used this file, mail-server/download/deb/latest/axigen_10.4.0-1_amd64.deb on the Axigen server.
So all SMTP-OUT sessions that are trying to deliver a message to a Gmail recipient are disconnected after 5 minutes:
2022-12-13 15:03:44 -0500 16 mail SMTP-OUT:00000001: >> Send last chunk of size 2444
2022-12-13 15:03:44 -0500 08 mail SMTP-OUT:00000001: Release mail 108CBD
...
2022-12-13 15:08:44 -0500 08 mail SMTP-OUT:00000001: Disconnected from 74.125.195.26
For testing purposes, could you please try to send a message from WebMail? Or those messages were already sent from WebMail?
Also, could you please send me (via direct message) one or two messages blocked into the queue (if not already removed, you may download them via WebAdmin > Queue > View Queue)?
I have no other ideas on this topic so let’s explorer any possible options we have at hand.
I looked at your profile and I do not see how to contact you. Please feel free to send me an email at eds@ {my username on the board} dot com. That address uses my email server I want to replace.
I have installed the Axigen server v10.4.0 twice on two clean Ubuntu 20.04 VMS. Both times it has had this problem. And even upgrading one to v10.4.1 did not fix this problem. The only to common items was my Axigen license and the server version.