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.

This error indicates you are sending email using a disallowed AOL.COM screenname as your FROM or REPLY-TO address, or as one of AOL’s affiliates from an unauthorized IP address. Example: Billing@aol.com

Clearly this is AOL attempting to minimize phishing and spoofing of the AOL brand. This is a great thing.
Unfortunately, there seems to be some problems with the current implementation. This rule is catching perfectly legitimate email. One report I have seen is that mail with @aol.com in the from address is getting rejected with this message. That means all those small businesses sending mail from their @aol.com addresses through an ESP are seeing problems. Another report I’ve seen is that email addresses with “a” “o” “l” in order (like, for instance, kaolin@somewhere.example.com) are also getting rejections.
It’s very possible that this filter is catching other mail, too.
Folks I’ve talked to are in touch with AOL and AOL is working on fixing the issue.
Note these do seem to be intermittent errors and not every email with an @aol.com address in the from line or some rendition of “aol” in the email address is getting bounced. But if you do start seeing increases in the number of AOL bounces and they are RLY:SN, this may be why. A short term work around will probably be to modify From: addresses where possible. Longer term, we’re just going to have to wait for AOL to fix things.

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

AOL update

A reader has been talking with AOL about the mtain* responses that people were receiving. AOL has said both responses mentioning mtain-*.r1000.mx.aol.com are actually DNY:T1 bounces that are being presented incorrectly. Both responses should be treated the same as 421 DYN:T1.

Read More

AOL: Still broken

I’m still hearing reports that AOL is still having problems accepting mail. I’ve also heard they’re still working on it. There is no information on when a fix may be finished.

Read More