Server suddenly blocked by AOL

Portal Home > Knowledgebase > Articles Database > Server suddenly blocked by AOL

Posted by badhat, 02-17-2011, 11:50 AM
After many years using one IP address, we moved to another facility so we had to change the IP address. We were initially blocked by AT&T but, after fixing the rDNS which was pointing to the hosting facility instead of our nameservers, we were removed from the list and all is well... except AOL, which starting blocking Email AFTER the rDNS was setup. They seem unable to be contacted. This should give you a good idea of the problems - you cannot contact the postmaster at AOL without using their "telnet tools" http://postmaster-blog.aol.com/2010/...ouble-tickets/ [mysite@myserver ~]$ telnet mailin-01.mx.aol.com 25 Trying 205.188.59.194... telnet: connect to address 205.188.59.194: Connection timed out Trying 205.188.159.42... telnet: connect to address 205.188.159.42: Connection timed out Trying 64.12.90.1... telnet: connect to address 64.12.90.1: Connection timed out Trying 64.12.90.98... telnet: connect to address 64.12.90.98: Connection timed out Trying 64.12.222.197... telnet: connect to address 64.12.222.197: Connection timed out At the moment, we've tried to tell anyone and everyone not to use AOL.
Posted by Patrick, 02-17-2011, 11:55 AM
http://postmaster.aol.com/ Have you contacted them through that site? AOL are usually pretty good about these things, make sure you have good IP reputation, SPF records and that your rDNS matches your server hostname / mail server address.
Posted by coderiser, 02-17-2011, 12:03 PM
yes rdns can be a major player in keeping your ip working with different mail providers
Posted by badhat, 02-17-2011, 12:28 PM
Take a look at what I posted and go to that link. You cannot use their form to contact them unless the results of the "telnet tools" is pasted. The form will tell you that what you typed into that field doesn't conform with what they are expected and the form will not submit. Try it yourself: http://postmaster.info.aol.com/cgi-bin/plugh/telnet.pl It appears I'm not the only one who cannot get past this step per that URL. I keep getting timed out as AOL passes the request from its own internal IP address to another, to another and then times out entirely. My IP Reputation is neutral. - My rDNS is setup but the namservers are domain1.net and the mail server I'm using sends mail from domain2.com. It has never been a problem and isn't anywhere else but AOL. - When I try to setup a feedback loop with them I get denied constantly - even setting up a feedback loop to send email to domain1.net directly (the same as the nameservers) - and then they paste the standard explanation here. how does anyone even send mail from a server that has more than one domain if they require the sending domain be the same as the rDNS results? - My NOC is the one that is listed as handling spam and abuse for this IP so I don't "own" the IP address although I am using it. Using WHOIS shows them as whom to contact for spam/abuse. Your Feedback Loop request, with the confirmation code 1297958327-845782, has been denied. Your web request has been denied because you do not appear to be the owner of the IP address(es) in your request. If you are in fact the owner, one of the following criteria must be met before resubmitting your request: * The RDNS for each IP shares the FBL email domain in common. Valid Example: FBL email address is aolfbl@accounting.aol.com 192.168.1.1 resolves to mailserver1.accounting.aol.com 192.168.1.2 resolves to mailserver2.accounting.aol.com *The DOMAIN WHOIS for each IP's RDNS shares the FBL email domain in common. The domain may appear in any of the listed email addresses. * At least one authoritative nameserver for each IP shares the FBL email domain in common. Valid Example: FBL email address is aolfbl@accounting.aol.com 192.168.1.1 authoritative nameserver is ns1.accounting.aol.com 192.168.1.2 authoritative nameserver is ns1.accounting.aol.com * The IP WHOIS information for each IP shares the FBL email domain in common. The domain may appear in any of the listed email addresses. Valid Example: FBL email address is aolfbl@abuse.aol.com 192.168.1.1 and 192.168.1.2 IP WHOIS: OrgName: Your Company Name ... NetRange: 192.168.1.0 - 192.168.1.255 CIDR: 192.168.1.0/24 NetName: COMPANY-1 OrgAbuseHandle: xxxx OrgAbuseName: abuse OrgAbusePhone: xxxx OrgAbuseEmail: abuse@abuse.aol.com ... * The ASN WHOIS information for each IP shares the FBL email domain in common. The domain may appear in any of the listed email addresses. Valid Example: FBL email address is aolfbl@abuse.aol.com 192.168.1.1 and 192.168.1.2 ASN WHOIS: OrgName: Your Company Name ... NetRange: 192.168.1.0 - 192.168.1.255 CIDR: 192.168.1.0/24 NetName: COMPANY-1 OrgAbuseHandle: xxxx OrgAbuseName: abuse OrgAbusePhone: xxxx OrgAbuseEmail: abuse@abuse.aol.com ... More about feedback loops can be found here: http://postmaster-us.info.aol.com/fbl/index.html. For more information on sending email to AOL, sender best practices, IP reputation and more, please visit our website at http://postmaster-us.info.aol.com. Thank You, AOL Postmaster Team Requested IP(s):
Posted by badhat, 02-17-2011, 03:37 PM
http://postmaster-blog.aol.com/2010/...ouble-tickets/ Somehow this URL disappeared. Others seem to have this problem as well. Unless I see something otherwise, it looks like it is AOL's fault and there is no way to remedy this.
Posted by Mat Sumpter, 02-17-2011, 03:53 PM
Since SMTP connections are not even completing, can you send to other mail servers? Just checking to make sure your ISP hasn't blocked tcp port 25 outbound on your connection.
Posted by badhat, 02-17-2011, 04:33 PM
Thanks - no, I have a dedicated and I should be fine. The SMTP completes fine everywhere but AOL where I am blocked: SMTP error from remote mail server after initial connection: host mailin-03.mx.aol.com [205.188.59.193]: 554- (RTRC) http://postmaster.info.aol.com/errors/554rtrsc.html 554 Connecting IP: xx.xx.xx.xx I just discovered a way to 'fake' the results of the test by putting in the information the postmaster wants to see to submit the form. Also, fortunately, after 10 tries, I was given approval with a feedback loop for my nameservers. What a horrific pain and a total disservice to AOL customers. We've been sending there without any complaint for almost 15 years and then this happened out of the blue. Taking care of it is beastly and even their link to a document for "more info" doesn't work. I'm saving my form to enter and, if anyone needs assistance, feel free to reach me. Thanks to all of you for trying to help remove the block. Fortunately I'm feeling it will be soon.

Add to Favourites Print this Article