AOL rejecting emails from postino1.discountasp.net?

It looks like AOL is currently rejecting emails we send automatically from our website (when someone places an order, creates an account etc.)

In the rejection email it's telling us it's getting a "421 DYN:T1" error, which according to this means that "The IP address you are sending from has been temporarily rate limited due to lack of whitelisting, unexpected changes in volume, or poor IP reputation".

By using this tool you can check the reputation of the IP of postino1.discountasp.net, which says that it is neutral, which is probably why it is being blocked.

Is it possible for you to contact AOL and apply to get this mail server whitelisted?

 

really MUST be fixed

"dealing w/ AOL is a real pain..."

Aww, that must be very tough on you.

It is not acceptable for MY emails to be blocked because of YOUR problems. This has to be fixed.

 

I'm pretty sure he said they were working on it

 

Do tell us all your solution to dealing with AOL. I would like to hear it.

Have you ever called your cable company or or any other service provider and been frustrated by the process? Well, multiply that several thousand times and you'll begin to get some idea of what it's like trying to get any information in to - or out of - AOL.

If you think we're sitting back sipping cocktails and staring at the clouds you're mistaken. We're doing everything we can do. But what we can do is limited.

 

Our mail admin spoke to someone at AOL and they have removed the block. It may take an hour or two for the removal to propagate.

Um, scratch that, I just received an email from AOL saying it could take TWO DAYS - though I expect they say that just to cover themselves. I would not expect it to take that long.

FWIW - the AOL guy said they are very understaffed at the moment and have been slow to reply to block inquiries.

Also, we tried to work around this yesterday by assigning a new IP to the blocked server, but the IP did not have a mail reputation so Gmail began blocking it and we had to switch the IP back.

 

Thanks for that.