>> Are those complaints or are they DMARC notices? > > complaints, en mass, by a n00b who just returned from vacation and > decided to expeditiously clear out his inbox. :-) He subscribed to > a list on 07-Aug using an outlook.com addr, and again on 27-Aug using > a @yahoo.com addr from a Comcast IP (73.53.12.230).
Happens. I do it, too. And sometimes even for mail I didn’t subscribe to ;) That’s part of the “fun” of running a mailing list. > >> From discussions in other places, it seems Microsoft is doing an internal >> handoff that’s breaking authentication and a lot of messages are coming back >> as “unauthenticated” or “SPF fail.” This is the kind of message I would >> expect if they’ve really broken things and are actually sending out DMARC >> failure notices. > > The only MS text is "complaint about message from 10.162.145.[0-9]+" , > everything else looks normal and good. They really broke something during a recent update. They are doing an internal forward and, from the outside, it looks like they never told their tools that they added an extra forwarding hop. It’s breaking authentication and, apparently, breaking some of their FBL reporting. I have to wonder if they’re counting those FBL hits against your IP or against their own. Ooooh. That could so complicate filtering if their tools are looking at the 10* IP and not the source IP. Hrm. THAT is an issue worth discussing with smart people. > >> Otherwise, have you created a JMRPP account with them and are you getting >> complaints? > > Yes, that is exactly why/how I received them. I'm simply surprised > that the rfc1918 space is contained in the subject. Yeah. Kinda weird. laura -- Having an Email Crisis? 800 823-9674 Laura Atkins Word to the Wise la...@wordtothewise.com (650) 437-0741 Email Delivery Blog: http://wordtothewise.com/blog _______________________________________________ mailop mailing list mailop@mailop.org http://chilli.nosignal.org/mailman/listinfo/mailop
