I'm just wondering if there was some bleed between the ML copies of the message and the personal traffic copies of the message.
For it to be blocked as spam, the system must have seen many copies... I guess enough people are sending out DCC hashes that enough of them added up and the direct email was blocked? 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: Monday, May 2, 2016 2:22 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 21:56 +0000, Michael Wise wrote: > So is the FORMERR ... just the resolver noting that EDNS is not > supported? Yes. 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? Yes. I don't think the MS dns servers are doing anything wrong. I rather suspect it is something in the dns client that is sometimes getting tripped up on the combination of short TTLs on a server that does not support edns. > Traffic to a mailinglist is scored with DCC? That would be me. The mailing list servers are whitelisted here for this list, but the MS servers are not. So the direct copy went thru the DCC filtering. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEAREKAAYFAlcnxMYACgkQL6j7milTFsHAwACfVbhMx920pYN+rWexwCFCBaFV EN4AoIlItXaDz6e79TFLwY0DtXE34pNk =G40z -----END PGP SIGNATURE----- _______________________________________________ mailop mailing list 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
