On 2021-11-23 14:47 -0600, Derek Martin wrote: > > sbcglobal.net will fail delivery of the message with the following error: > > > > <user>@*sbcglobal.net*: 550 5.7.1 Connections not accepted from > > servers without a valid sender domain.alph758 Fix reverse DNS for > > 198.51.100.1 > > It's just told you what the problem is, and you've misunderstood or > ignored the explanation, and come up with a solution that just happens > to work by coincidence, because it *also* effectively changes the > piece of data that actually matters...
My mail domain has had correct reverse DNS entries for ages. As soon as I received the error I verified it from multiple hosts to be sure. It's not a reverse DNS configuration problem on my side. > Bottom line: This is NOT a Mutt problem. It's a misconfigured > MTA/host problem. Without a MUCH better justification, this patch > should be rejected: It only allows the user to configure their message > ID improperly. But then again, I made that same argument for the > entire message ID format feature, and pointed out that if you let > people do that, they will... I never said it's a Mutt problem. I said I found a way to work around it using Mutt and asked to codify the solution to make it easier to use. I've been running email on this domain and others for more than 20 years. I'm acquainted with many of the day-to-day problems associated with misconfigured clients, servers, and DNS as it relates to email. My first assumption when I got the notice was that I missed something. I checked it thoroughly. The most likely answer is it's server configuration problem at ATT, whether that be their MTAs or DNS look-up, I can't say. I can say that there are complains going back to 2017 about ATT and related companies rejecting email for failed rDNS look-ups where the admins have verified their configurations are correct. In 2018 Network Solutions posted a notice confirming that ATT (and related companies) were returning erroneous rDNS failures but that their rDNS look-ups were working.[0] Here's a complaint from an outlook.com user who got the error in April of 2021 while sending to an att.net user.[1] Bottom line: It's not a misconfigured MTA/host problem *if* you mean my MTA. > > I know this is related to Message-ID... I'll back off this claim because I can't prove it beyond doubt. I've heard from another mutt user who made the same change and that it resolved the issue for them as well, but two data points aren't enough to prove much. Perhaps we both got lucky and the mutt changes coincided with a DNS fix at ATT, or maybe our subsequent emails went through a different server that doesn't have the problem. As for making the fqdn of the From-address available during Message-ID generation, I see value in it regardless. But it's not my software. I don't get to decide. I'll leave it as it always was: a suggestion. Cheers, --Aaron [0] <https://www.netsolinc.com/prodigy-email-issues/> [1] <https://answers.microsoft.com/en-us/outlook_com/forum/all/connections-not-accepted-from-servers-without-a/a777771c-93bc-43b7-83e3-ae82c8d7c228>
