Apologies if this needs to go elsewhere; pointers, if appropriate, will be welcome.
When I try to mail a spoof report about my home system, mikea.ath.cx, I get back "could not send" and "returned mail" notices: > The original message was received at Mon, 4 Jan 2016 10:16:36 -0600 (CST) > from localhost [127.0.0.1] > > ----- The following addresses had permanent fatal errors ----- > <[email protected]> > (reason: 451 #4.1.8 Domain of sender address <[email protected]> does > not resolve) > > ----- Transcript of session follows ----- > ... while talking to mx2.paypalcorp.com.: > >>> MAIL From:<[email protected]> SIZE=15200 > <<< 451 #4.1.8 Domain of sender address <[email protected]> does not resolve > ... while talking to mx1.paypalcorp.com.: > >>> MAIL From:<[email protected]> SIZE=15200 > <<< 451 #4.1.8 Domain of sender address <[email protected]> does not resolve > <[email protected]>... Deferred: 451 #4.1.8 Domain of sender address > <[email protected]> does not resolve > Message could not be delivered for 5 days > Message will be deleted from queue Paypal has no problem sending mail to *me*, which implies that at least some set of their nameservers can resolve mikea.ath.cx just fine. It's just that the nameservers they use on their inbound mailserver(s) (mx[12].paypalcorp.com) don't resolve mikea.ath.cx at all. The nameservers associated with paypal.com, as shown in `dig paypal.com`, are a totally disjoint set (ns[1234].p57.dynect.net) which *do* resolve mikea.ath.cx, again as shown by `dig mikea.ath.cx @ns[1234].p57.dynect.net`. Does anyone have a handle on how to get in touch with someone who can get this fixed? It's to paypal's benefit, as it is spoof reports that they've said they want to get. Moreover, if it's happening to me, it probably is happening to other people. -- Mike Andrews, W5EGO [email protected] Tired old sysadmin _______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
