brylon@oit.rutgers.edu writes:
Thanks for the response. You are correct in the fact that I've enabled/configured the ARC module, however, I don't think Mailman is adding that (malformed) header considering I'm now HOLDing the test email(s) sent to our postfix inbound MX servers *before* they are LMTP'd to the Mailman server and its already there when I postcat it.
OK, thanks for that clarification. I feel better (but will still check it! just a bit less urgently ;-)
What do you still need from us? I guess the easiest thing for us would be to catch the Exception in our ARC module, and ignore nonconforming Authentication-Results, so that there will be no ARC signature from Mailman on those posts. Will that do? (Note that "ignore and/or delete" is the RFC recommendation. I'd need more than "it would be nice" as a reason to try to parse non-conforming A-R. Mark's experience with parsing *conforming* (non)delivery notifications is quite a deterrent to that.)
At the same time I also can't fathom that Office365 has this wrong (still?) and no one has noticed/complained?
I guess I would say, how would we know if there were complaints? ARC is a very recent addition to Mailman, so you wouldn't necessarily see it here yet, and Office365 doesn't have a public bug database AFAIK. ;-) Microsoft (and other > 1G$ corporations) have a long history of "embrace, extend, and drive conformant implementations out of business".