Just to pile on ATT issues. I assume you are trying to deliver to an att.net address, these are the emails they provided for free to dialup/broadband users, its also legacy prodigy.net.
What you are experiencing is not new news. Yes, ATT refuses email from any new IP - regardless how clean or dirty it is. And yes, the reason is always: 553 5.3.0 alph766 DNSBL:RBL 521< 208.88.X.X >_is_blocked.For assistance forward this error to abuse_...@abuse-att.net <mailto:abuse_...@abuse-att.net> Its possible some “select” IP space/ASNs get better treatment, but I have not seen evidence of that. So by that logic, any new email provider or email host will have a hard time sending to att.net <http://att.net/>. I understand “my server, my rules”, but this behavior is silly. My personal opinion is ATT does this on purpose to accelerate the death of their legacy email commitment. For starters, they dont want to support this old email anymore (all ISPs have long abandoned email), but some old contracts are forcing them to keep it for those who are grandfathered in. If you are a legit att.net <http://att.net/> email user, life must be hard for you and you likely miss some emails. This means more people abandon their old ATT.net <http://att.net/> email and get a gmail account. Over time the numbers dwindle down. Also, this is ATT we’re talking about... Its possible that after a long time of sending low volume email (that 553’s) they might let it through after you tolerated the punishment, or they eventually answer the RBL request. Good luck. Maybe redirect your att.net <http://att.net/> email to a smarthost service that is able to deliver to att (Amazon SES maybe?) -John > On Jul 5, 2024, at 10:30 AM, Scott Mutter via mailop <mailop@mailop.org> > wrote: > > Anyone from AT&T on the list that can assist with the blacklisting of the IPs: > > 23.239.97.150 > 5.101.141.35 > > Message is > > 553 5.3.0 alph749 DNSBL:RBL 521< 23.239.97.150 >_is_blocked.For assistance > forward this error to abuse_...@abuse-att.net > > As is the usual case, I've gotten no response from an inquiry to > abuse_...@abuse-att.net. I sent one to abuse_...@abuse-att.net for > 23.239.97.150 on July 2nd and no response. To be fair, I wrote > abuse_...@abuse-att.net about 5.101.141.35 just yesterday (July 4th) so it > really hasn't been 24 hours yet, but past experience has taught me that I > rarely get a response from an inquiries sent to abuse_...@abuse-att.net. > > I suspect that this is being blocked because these are new IPs that AT&T has > never received mail from, so they block them by default. Is there an > official way to inform AT&T before trying to send mail from new IPs that new > IPs will be sending mail? As far as I know AT&T is the only service that > outright blocks messages from new and unseen IP addresses by default. > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
