Removing IP from AOL email Black List postmaster

Website Developer SydneyI’m finding the AOL process really really annoying. We have been trying to clear up blacklist and reputation problems with a new IP range that was previously abused.

AOL have some tools that pretend to help. What you need to know is this.

1. Ensure your mail server IP has a RDNS – so when you do an NS lookup on the IP address it will show a name, like

2. Setup an email account like abuse@ or postmaster@  that domain. Make sure you get that mail.

3. Ensure that you verify with AOL that you are the admin for that RDNS lookup name. That is by submitting a ticket called Feedback Loop here:

4. Wait till they verify your Feedback Loop. AKA. that you are getting mail on that domain.

6. Use this link:
to work out the IP of an AOL mail server.

7. Work out what code error is given when you try to connect from your mail server using Telnet. Follow these instructions. but use the IP address and port 25 of the AOL mail server from step 6 above.

8. Look at the error result and compare it to this page:

9. Follow the support request process from that page, to submit a ticket to have them fix things up.

Easy as that.!

Imagine if we had to do that crap for every email domain in the world. This was a recent blog from AOL about their update:

We are in the process of automating email problem report resolution. This is a mid-term project, and is being implemented in stages on a queue-by-queue basis. (Ex: Each unique error code type represents a different queue, as do feedback loop and whitelist requests. )
The last couple of months were spent migrating our sundry ticketing systems onto one common platform — essentially readying a back-end for the front-end logic flow that you will interface with. We are excited to finally be addressing the part of this project that will offer, in most cases, immediate resolution to your issues.
We are starting with router-level queues, the first of which will be RTR:BB errors. I will post on our progress as we push the code into production, along with what ticket submitters should expect with the automated process specific to the queue addressed. If you are seeing problems with the queues in transition, please comment on that particular blog post, and we’ll take a look.
Meanwhile, our Postmaster staff will continue handling every ticket we receive.
Thanks for your patience and support during this transition!


This was my comment.

1. Good that you are improving things. Sucks that your process is so stupid in the first place. An example of how frigging annoying I am finding things.
We at: have been forced by a chapter 11 of an upstream provider to move all our servers to a new IP range.
First thing we did was to setup RDNS and check mail reputation (on all the major Black Lists, and What we found was that the IP range has been abused. So we set about cleaning that up.
Naturally we checked AOL, and found that the IP was "undisclosed" reputation. Helpful Right… NOT!
But it does not show AOL was listing it.
So we move and fire up services. THEN and only then do we find out that AOL does have the address on a BL and mail cannot be delivered.
How about tools that work, and a process that works to allow proper checking/de-listing.
The ironic part of dealing with your 1990 process, is that it really does not work as well as other systems. AOL users get more spam than many other reputable spam systems. There is even free spam software services that do better.
So why stick with such a lame process, when the end result is HEAPS of false positives?


14 thoughts on “Removing IP from AOL email Black List postmaster”

  1. William Faulkner

    It’s not got any better – I’ve just set up a Spam Titan Private Cloud – rDNS, SPF – everything covered. Checked the IPs with a good selection of RBLs, no problems.
    After going live discovered that AOL had one of the nodes on a block list. 3 days of messing around with AOL PostMaster tickets resolved this… one week later and a vast 186 emails to registered clients with AOL addresses, I now have 32 AOL emails in my deferred queue as AOL ‘will not talk to me’.
    Beyond frustrating…

  2. I’ve given up at this point and I tell my users to tell their contacts that user aol to get themself a proper mailprovider. Most of them understand and quite a lot people actually did move to a new provider 😉

    1. We (InteractiveWebs) can provide hosted email services if you have any clients who would like to spend a few $ on a domain and have ownership over their own email forever.

  3. Old post here, but wanted to chime in and personally thank you for your step by step process here. Two years after you posting this, I’m afraid AOL is still doing the SAME crap with blacklisting IPs and giving you the run-around and taking forever in allowing email through. I can imagine they get inundated with VALID requests, tying up their customer service dept and unable to keep up with it all. I am still actually waiting to get delisted and have already taken it to Twitter and filed multiple service tickets all the while making my own clients do the same thing.

  4. I’ve given up on AOL. We just let our students know that AOL has a bad system and their email for completion of the course will be blocked by AOL. The hard copy mailed to them is what they have to have anyway. I suggest to them they find another email provider. We have Sitelock and aren’t blocked by any other company. AOL is a waste of time dealing with.

  5. I work for a large retailer and have been trying now, with no success, to speak to a live individual about a throttling issue I am having sending mail to AOL. Gone through the Postmaster site and put in multiple incidents. Requested whitelisting my IPs, spoken to support that just keep asking me what my AOL email address is but can not transfer me to a Level 3 Engineer for support. Does anyone have a good phone # to reach someone other than a end user support person? I have 1000’s of emails queued up and sending at a snails pace.
    thanks for any help

  6. If you have any email campaigns aol will likely block every outgoing email from that IP. Never setup an email campaign from your own IP. I’ve also noticed many hosts do not setup the rdns properly. They say it’s all setup but it’s not.

    Telling aol customers to switch is not what to do. Yahoo works very similar to aol so now you can’t send to yahoo either.

  7. getting really upset of this AOL, my IPs are getting deferred, and the msg error they show me is: Error: “421 4.7.0 [TSS04] Messages from xxxxxxx temporarily deferred due to user complaints…” that “user complaints” what that mean ? cuz my ips are not listed not even my domaines everything is clean.
    100 IP and cant send even 1K emails to aol, this is unbelievabe. is there any way to stop that ? SPF and DKIM all are ACTIVE. is that about warming up ? if so then what is the right way to do it please?

Leave a Reply

Your email address will not be published. Required fields are marked *