So is the FORMERR ... just the resolver noting that EDNS is not supported?
If so, I'm uncertain of the issue. We don't use EDNS here, so that's what the “our” servers should be doing, yes? Also, when I replied (“ALL”) to this thread a bit earlier, my response was bounced by one particular recipient with: Error Details Reported error: 550 5.7.1 Mail rejected - dcc score 1000 Retry count: 1 DSN generated by: BY2PR03MB409.namprd03.prod.outlook.com Remote server: * Traffic to a mailinglist is scored with DCC? Aloha, Michael. -- Michael J Wise | Microsoft | Spam Analysis | "Your Spam Specimen Has Been Processed." | Got the Junk Mail Reporting Tool ? -----Original Message----- From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Carl Byington Sent: Thursday, April 28, 2016 2:16 PM To: mailop@mailop.org Subject: Re: [mailop] DNS Errors for Microsoft Hostnames -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Thu, 2016-04-28 at 20:57 +0000, Michael Wise wrote: > If the "Aware" flag expired, would best practice not be to check that > first rather than presuppose that the facility does exist? The check for "edns aware" involves sending the query with edns extensions. If the reply is formerr (or possibly others?), then you can remember that this server does not understand edns, and repeat the query without it. If you just do the first query without edns, there is no mechanism to then learn that that server does indeed understand edns. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEAREKAAYFAlcifY8ACgkQL6j7milTFsEyTgCfbLe36v3LuECg+Ma4/mjxq52c C9oAnjFeZYZjl2//eCsWM3NvkeWwthUy =H2pv -----END PGP SIGNATURE----- _______________________________________________ mailop mailing list mailop@mailop.org<mailto:mailop@mailop.org> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
