EmpireAeroCenter
asked on
Mail not going out to certain domains
We recently switched ISPs and started having issues with email going out to certain domains. It will just sit in queue. an SMTPdiag /v on these domaines show the following.
Error: Expected "220". Server is not accepting connections.
Failed to submit mail to mailin-02.mx.aol.com.
Connecting to mailin-01.mx.aol.com [64.12.139.249] on port 25.
Connecting to the server failed. Error: 10060
Failed to submit mail to mailin-01.mx.aol.com.
Everything I have found online referes to a reverse DNS issue, I have repeadadly verified that our DNS records are setup properly with the new ISP. Does anyone have any other suggestions what it could be?
Error: Expected "220". Server is not accepting connections.
Failed to submit mail to mailin-02.mx.aol.com.
Connecting to mailin-01.mx.aol.com [64.12.139.249] on port 25.
Connecting to the server failed. Error: 10060
Failed to submit mail to mailin-01.mx.aol.com.
Everything I have found online referes to a reverse DNS issue, I have repeadadly verified that our DNS records are setup properly with the new ISP. Does anyone have any other suggestions what it could be?
ASKER
The cutover was last wednesday and of course the new ISP didnt do our new DNS settings until that afternoon after we yelled at them for it. I will keep that time frame in mind. The problems are with AOL, a couple Roadrunner domains {nycap.rr twcny.rr tampabay.rr}
You could try manually submitting a message to each using Telnet. I suspect the problem is likely to be caching on the part of AOL if you've checked all your records and found them to be correct.
Chris
ASKER
Sorry, forgot to close this question
After extensive testing we learned via SMTPdiag tool, that the new IP we were using was blacklisted by some of the commonly used personal email providers like Gmail, yahoo, and AOL. It was a headache getting this cleared but we did contact the locations where our mail was getting rejected and they were willing to work with us. Our ISP was also kind enough to contact some of the blacklisting organizations to let them know that the IP was re-assigned to a legitimate company.
After extensive testing we learned via SMTPdiag tool, that the new IP we were using was blacklisted by some of the commonly used personal email providers like Gmail, yahoo, and AOL. It was a headache getting this cleared but we did contact the locations where our mail was getting rejected and they were willing to work with us. Our ISP was also kind enough to contact some of the blacklisting organizations to let them know that the IP was re-assigned to a legitimate company.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It's worth noting that AOL are slow when it comes to seeing DNS updates. They do a lot of extra caching that you only see on providers of their size.
Is the change a very recent one (less than a week ago)?
Chris