After receiving two rather patronising emails from Del Monte this morning, I decided it was time to investigate. Why were game serverÂ customers not receiving their welcome emails?
I installedÂ Sendmail in a hurryÂ on Agatha (our 2nd webÂ server) a short while ago via a RPM debian install. It failed to start first time, so after some sendmail.mc tweaking, it happily started. We did not need it before, you see, as there were no applications running on the machine that needed the facility to send outgoing mail. Now, however, we have automatic game server installations on the go, and as such customers need their welcome emails with control panel login info and the sort. Del Monte tested the system and found he didn’t receive his welcome email. He was not happpy.
After looking through the SendmailÂ config files, and finding that there were no obvious issues, I decided to look at the mail.log file. I was greeted with 3453 lines of deferred 127.0.0.1 relay denied, connection refusedÂ errors. Joy.
You can telnet to the machine locally, the hostnames are correctly configured, the access.db file is set to relay local mail and the config files are all set. So what on earth is causing the increasingly large mail queue to fail to send?
Thanks goes out to Rob at Bluesquare for fixing this one! It seems a blind squirrel does sometimes find a nut ;o)
All emails in the queue (mainly customer welcome emails) have now been sent successfully. Apologies to customers kept waitingÂ in the dark!
This is what Rob had to say:
By default the local submission agent (as configured in submit.cf/submit.mc) talks to localhost on port 573, but it wasn’t set up to listen on that port. I went into /etc/mail/sendmail.mc and added another daemon options line to set up another MTA port on 573 on localhost and then ran ‘make’ to regenerate sendmail.cf