I noticed something similar - they are claiming a domain does not resolve, when it definitely does. em-270068.wordonfire.org is a CNAME that resolves to A record of 52.128.42.8 (see below). This started in the past week
451 4.1.8 Domain of sender address bounce-xxxxxx...@em-270068.wordonfire.org does not resolve Thanks, Alex -- Alexander Burch ActiveCampaign / Senior Deliverability Engineer abu...@activecampaign.com 1 North Dearborn St Suite 500, Chicago IL, 60602 <https://www.facebook.com/activecampaign> <http://www.twitter.com/activecampaign> <https://www.linkedin.com/company/activecampaign-inc-> <https://plus.google.com/107063868317743606466> <https://www.activecampaign.com/sig/?u=aburch&c=1> On Thu, Feb 20, 2025 at 1:24 PM Rob McEwen via mailop <mailop@mailop.org> wrote: > Starting earlier today (Feb-20-2025) AT&T/Prodogy/Yahoo started rejection > my users' emails due to my sending-IP-address (204.9.77.40 > <http://204.9.77.40>) > allegedly not having rDNS, except it does! This is happening to emails sent > to the email addresses hosted at the following domain names: > prodigy.n > > > > > > > > > > > > > > > > > > > > > > > > > > > <https://login-usb.mimecast.com/u/login/?gta=apps&link=cybergraph-report/eyJhbGciOiJSU0EtT0FFUC0yNTYiLCJlbmMiOiJBMjU2R0NNIn0.DEQK59fPBimn1jhPmphRuYOLjDhlPsnHR-9mt164ugOMD_h0SbxxAe7zeoNuP9CC9LGZ18oUexfxcsiTSj7wx-WNH0niGtEEZNdjsgyReOiSF22ZQ10m1gLw--JSOaT7CVZsEUNeg-BkCTfrfCXQshYJFz1S2Q81on_7RJJWAr7UFcWbCph1mvtPKNdprXBibtLNQKZtKI8XqAwV09hDS8BB4TZwX8coD7ykhKN1YlzFS1CxAIssRzqqnMpj8ZCRUb63Mlj6VxvddFOkM2VL8nHfNK1yHb9PWSUAredMgGzJ2u8sTJtAyqqm4-iDMNisp275dzVIhAlFj0mHU-wCDA.i5YPt42YJbdCZQtV.LXYTEQovvFW-ehn3YeB4QUEU-dABxixOHU9dFS8z3Zi1JSziE33e25LR_0PX9ep2Vac196KyuaqNceGplIZVrtG3zHIhVjgLy_ugJwPURx_iFWDFuE_eSdQ_DN8qnrdBJb8gc2C-bQ2Mle7zFbNjC3cR2A5sJ710DeiS_1TNw94yASfkJWwJ__iEp9LgC0e-aj5XIIFEMFrSQFI2EF4guY5tk9lQKpS7m-Pc9YMUWgIxsCfUKMAX8FkH-yQaRGGxL_uDsoBqeYXqDzJab3PmrvI0COsnYxju1mYKozoHzUPdoU0k1u2QqQJQfLi8BcQanNr6dlJpA5oZtZd6o4wmHM8mRm8N1LhIE2FyV_0YFEK6U0eIPetu1QLIZL9Y8ZdSIdu79mC1rxfYCnOkA3Vr0p_JNfv2W6ieqdZggT5_fBQyuBjqITTA200Sq86O53ZO_ZR1YZ--mOQv3X-Vk95o9dU7AoF6TzRnxUiMEfHetoMnZGeGlfyvtfXOg9GrW51Ryaimbaqeb9wJe7BRhk4o5p-qWTEB.kv7hw1zoZPN4njMOTpcZ0Q> > CGBANNERINDICATOR > Starting earlier today (Feb-20-2025) AT&T/Prodogy/Yahoo started rejection > my users' emails due to my sending-IP-address (204.9.77.40 > <http://204.9.77.40>) > allegedly not having rDNS, except it does! This is happening to emails sent > to the email addresses hosted at the following domain names: > > prodigy.net > bellsouth.net > att.net > > And *this error is ONLY happening when connecting to either > 144.160.159.21 > <http://144.160.159.21> > or 144.160.159.22 > <http://144.160.159.22>* > > When my users emails route to their *other* IPs - 144.160.235.143 > <http://144.160.235.143> > and 144.160.235.144 > <http://144.160.235.144> > - those are not having any problems. And I'm not seeing any such "no PTR" > or "no rDNS" rejection messages with any other email systems that my users > send to - and I have very good telemetry on rejections of emails sent by my > system. > > HERE IS THE ERROR THAT IS BEING RETURNED: > *550 5.7.1 Connections not accepted from servers without a valid sender > domain.flph830 Fix reverse DNS for 204.9.77.40 > <http://204.9.77.40>* > > And other times, this error is returned: > *451 4.1.8 Client IP address 204.9.77.40 > <http://204.9.77.40> > does not resolve.flpd569.Fix reverse DNS.For more information email > postmas...@prodigy.net <postmas...@prodigy.net>* > > But every time I do rDNS lookups on *204.9.77.40 > <http://204.9.77.40>*, > from all various systems, I consistently get this answered with > "*mail.invaluement.com > <http://mail.invaluement.com>*" > - so I can't get it to fail. (And it has RCrDNS since this hostname > resolves back to this same IP address) > > I asked my IP provider is they are having any issues with rDNS queries > getting answers - and they claim that they're not having any issues. Then I > tried to email support addresses at AT&T/Prodogy/Yahoo, but they are also > returning back with this same error. > > Anyone else having this issue? And suggestions? Is there anyone on this > discussion list who is with AT&T/Prodogy/Yahoo and who can assist this? > > Thanks! > > Rob McEwen, invaluement > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > > https://list.mailop.org/listinfo/mailop > >
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop