Mail problems at AOL

We cannot help endusers troubleshoot AOL connection problems. Please do not call. Please do not write. You need to talk to AOL. We are not AOL. We cannot help you. 


 
Over the last few months there have been ongoing mail problems at AOL. These problems are all over the map and are resulting in a lot of delayed and unsent email. People are reporting a number of different error messages from AOL mail servers. These messages don’t seem to always be accurate or correct.
A couple examples:
SMTP error from remote mail server after end of data: host mailin-02.mx.aol.com [64.12.90.65]: 521 5.2.1 :(CON:B1) http://postmaster.info.aol.com/errors/554conb1.html reported by the owner of a low volume discussion list with paying subscribers that should have zero complaints.
delivery temporarily suspended: host mailin-01.mx.aol.com[205.188.146.193] refused to talk to me: 421 mtain-dg03.r1000.mx.aol.com Service unavailable – try again later reported by all sorts of senders.
205.188.190.2 failed after I sent the message. Remote host said: 521 5.2.1 “TempFail” reported by a small mail host.
554 mtain-dc03.r1000.mx.aol.com ESMTP not accepting connections reported by an ESP.
421 4.7.0 mtain-dg05.r1000.mx.aol.com Error: too many errors reported by a university, a mailserver vendor and a bunch of ISP and telcos.
This is not a constant or consistent set of errors. It is coming and going, with AOL reporting things are fixed and senders reporting queues emptying. However, every time it seems to be fixed, something else breaks.
There isn’t much anyone outside of AOL can do, though. This has to be fixed internally by their engineers. I’m afraid this is just the result of a highly complex system that is failing due to bit rot, though. Which means only significant investment in time and programming power can fix this for all of us. I do hope I’m wrong.
It’s weird to be writing this blog post the same day I found out that Jay Levitt, one of the original AOL mail system architects has died. I didn’t know Jay well, although he did post a comment here once or twice. I haven’t heard any details, yet, but it’s strange to be writing about AOL mail today.
Update Feb 8, 2016: AOL users are having problems logging in. Word to the Wise cannot help you. Please do not contact us for help. Contact AOL directly.

Related Posts

AOL transmitting 4xx error for user unknown

AOL is currently returning “451 4.3.0 <invaliduser@aol.com>: Temporary lookup failure” in some cases when they really mean “550 user unknown.” This message from AOL should be treated as 5xx failure and the message should not be retried (if at all possible) and the failure should be counted as a hard bounce for list management purposes.
This is something broken at AOL’s end, and the guys with the magic fingers that keep the system running are working to fix it. Right now there doesn’t seem to be an ETA on a fix, though.
Even if you are a sender who is able to stop the retries, you may see some congestion and delays when sending to AOL for the time being. Senders who don’t get the message, or who are unable to stop their MTAs from retrying 4xx mail will continue to attempt delivery of these messages until their servers time out. This may cause congestion for everyone and a noticeable  slowdown on the AOL MTAs.
AOL blog post on the issue
HT: Annalivia

Read More

Bounces, complaints and metrics

In the email delivery space there are a lot of numbers we talk about including bounce rates, complaint rates, acceptance rates and inbox delivery rates. These are all good numbers to tell us about a particular campaign or mailing list. Usually these metrics all track together. Low bounce rates and low complaint rates correlate with high delivery rates and high inbox placement.

Read More

AOL bounces and false positives

A number of people have been seeing an increase in AOL bounces over the last few days. Some of these are the new rejection 554/421 CON:B1 message. This is, basically, you’ve topped our thresholds, back off.
The other one is a bit more interesting. The error message a lot of people are seeing is 554/421 RLY:SN. Senders should only be getting this error message when they are sending email from a banned address.

Read More