10-26-2016 3:27 PM
Hi, I'm the syadmin of an ESP. For some reason most of our users with ATT email addresses are unable to receive emails from the system. We've tried numerous times reporting the issue to ATT blocks, however the issue still exists and our users are getting frustrated. Can you help please?
This is the ATT error message from our email server. We use Elastic Email as our Email service provider. They believe you are blocking our domain for some reason, as they have already moved us to another ip.
Here's an example of the error we are getting:
553 5.3.0 alph154 DNSBL:RBL 521<126.96.36.199 >_is_blocked.For information send an email to firstname.lastname@example.org
This affects most of the IPs in our netblock (188.8.131.52/24) but not all.
We've reported this many times now and gotten no reply. It's been over a month. We've gone through every remediation step listed here:
Filled out the form here a number of times:
I tried this form as well:
Any help would be much appreciated!
Solved by: Go to Solution.
12-31-2018 8:51 PM
I wish to add my voice to the chorus of thousands of legitimate email providers who have posted on this forum about their email server IP addresses being erroneously blacklisted by AT&T. Like all the others I have followed the guidelines suggested by AT&T and have repeatedly emailed email@example.com for redress. And like everyone else, all I ever receive are automated replies saying AT&T investigates every request and will remove the block in 24-48 hours, which they never do.
I recently set up a new dedicated server with a well-respected hosting provider. I immediately tested the IP addresses assigned to the server and found that none of them appeared on any searchable Real-time Blackhole Lists. It was only after I had fully configured the server, firewall, outbound email restrictions and reverse DNS that I sent an email to sbcglobal.net to test whether the IP addresses were blocked. They all were. With the assistance of the hosting provider I then tested another series of IP addresses and they were also blocked. It appears that AT&T does not blacklist individual IP addresses, but entire netblocks.
I don't expect this post to result in de-listing of my IP addresses, so I'm not going to bother posting them. I just think it's important that the extent of this problem is documented and understood. Thousands of people have reported this problem in this forum so we can assume that tens of thousands have had the same problem but have not found this forum or bothered to post. That's not tens of thousands of email users, it's tens of thousands of email service providers, each representing hundreds or thousands of email users unable to send mail to their family or friends who are customers of AT&T. The extent of this problem is likely to be many millions of legitimate email messages being blocked every day by AT&T.
I suggest the following solutions:
1. AT&T is obviously incapable of maintaining their own RBL (Real-lame Blackhole List), so they should simply subscribe to one or more legitimate Real-time Blackhole Lists, such as SpamCop, Spamhaus, SORBS, etc. Those RBLs are well-maintained and responsive to de-listing requests.
2. Until this problem is resolved, every affected email service provider should block incoming mail from AT&T and its affiliate domains. There is no reason for our email users to be bothered by AT&T customers if they will be blocked from responding.
01-24-2019 4:10 PM
PLEASE UNBLOCK OUR IP's!
We have sent multiple inquiries over multiple days and the following IP is still blocked.
Our customers are missing important transactional emails.
01-26-2019 12:44 PM
Same problem as many others here- ATT reports that my server's IP address is on their blocklist.
Have tried emailing firstname.lastname@example.org many times and have included all information including copies of the bounce messages and the server IP address; haven't received any reply aside from the autoresponder.
Server's PTR record is correct and is not listed in any of the blocklists checked by sites such as mxtoolbox.
Server's IP address: 184.108.40.206 (an AWS address)
Meanwhile, my customers are complaining because they can't get emails through to sbcglobal addresses... this is really frustrating.
01-29-2019 9:20 AM
It takes too long to get this resolved. I literally cannot talk to other moms who have AT&T email. We are working on a musical with time -sensitive information and a group of 100 volunteers. I am now stuck - helpless to communicate to the group.
02-04-2019 10:53 AM
We are having the same problem.
Can we please have 220.127.116.11 removed.
This is a legitimate business and this is hurting our business!!
Thank you in advance!
- edited 02-18-2019 11:53 AM
Hi there we are being blocked as well:
Rejected (18.104.22.168:25:553 5.3.0 flpd576 DNSBL:ATTRBL 521< 22.214.171.124 >_is_blocked.For assistance forward this email to email@example.com(at FROM))
Please remove our IPs:
03-05-2019 11:06 AM
Is firstname.lastname@example.org not being monitored any more?
How do we get off of AT&T's blocklist. It can't be this hard to get in contact with a real person to look into this.
03-05-2019 11:18 AM
03-05-2019 11:24 AM
Actually, I originally wrote them on February 8th about this. Haven't heard a peep from them.
They don't care. We're not a big company. We don't have enough of a following to inflict any harm to them. So what if our users can't email AT&T users... who cares! We're just little peons.
03-06-2019 9:16 AM
PLEASE HELP! I was migrate to a new server but the ip is blocked for ATT, the IP is 126.96.36.199.
Thank you for your help.
03-08-2019 2:28 PM
I filled out the form two weeks ago and have contacted you over the provided abuse email multiple times.
Can you please remove:
It is 100% clean.
03-10-2019 5:28 PM
As of 1/9/2019, I can't receive any emails from my son's school (all communication is via Memberhub,
188.8.131.52), and this is causing huge problems. Everything was working fine for 3+ years until now.
PLEASE REMOVE 184.108.40.206. Memberhub is a fully legit service.
Visit these related resourcesView Email Help!
|12-11-2018 5:27 PM|
|01-16-2019 11:00 AM|
|12-22-2017 1:21 PM|
|08-09-2017 11:17 AM|
|07-30-2018 3:18 PM|