For messages sent from Office365, Microsoft applies an initial ARC set, and declares the message to be DMARC-compliant. I do not think Microsoft should be passing judgement on messages that it is originating, or attributing an SPF result to a message that was only just submitted with SMTP AUTH.
But this situation does point to the complexity of trusting and interpreting the ARC chain, which is unfortunate. On Thu, Sep 23, 2021 at 5:08 PM Brotman, Alex <Alex_Brotman= 40comcast....@dmarc.ietf.org> wrote: > Murray, > > > > We’ve started (relatively recently, in volume) logging ARC data so we can > try to make some informed decisions going forward. We’re not yet acting on > anything as a result, nor writing into the message. We’re also not doing > anything when mail is being forwarded. We’ll hopefully have more > information/data available to share in the future (may not be the very near > future given other projects going on). This isn’t a guarantee that we’ll > fully adopt ARC in the future, but enough to say we’re logging/analyzing > things. > > Random thing while looking at some data just now .. At least one message > apparently came through with seven ARC sets. > > > > Let me know if there’s anything I can answer at this point. > > > > -- > > Alex Brotman > > Sr. Engineer, Anti-Abuse & Messaging Policy > > Comcast > > > > *From:* dmarc <dmarc-boun...@ietf.org> *On Behalf Of * Murray S. Kucherawy > *Sent:* Wednesday, September 22, 2021 4:30 PM > *To:* IETF DMARC WG <dmarc@ietf.org> > *Subject:* [dmarc-ietf] Experiments > > > > Is anyone in a position to comment on the ARC and PSD experiments and how > they're progressing? Deployment status? Data acquired thus far? > > > > -MSK > > > _______________________________________________ > dmarc mailing list > dmarc@ietf.org > https://www.ietf.org/mailman/listinfo/dmarc >
_______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
