[Taking my reply to the initial thread so not to clog this one] On Tue, May 30, 2017 at 9:39 AM, Scott Kitterman <[email protected]> wrote:
> On Tuesday, May 30, 2017 09:34:49 AM Seth Blank wrote: > > Resolved items: > > - Handling of multiple incoming AR headers (resolved, but language not > yet > > in spec) > > If this is resolved in favor of not handling multiple AR header fields > (which > IIRC is the plan), then something needs to specify the combination is > required. I think that something needs to be a DMARC document, not ARC, > because this is a requirement that's being imposed on all DMARC AR header > field providers regardless of if they care about or participate explicitly > in > DMARC. > > Scott K > > _______________________________________________ > dmarc mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dmarc > -- [image: logo for sig file.png] Bringing Trust to Email Seth Blank | Head of Product for Open Source and Protocols [email protected] +1-415-894-2724 <415-894-2724>
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
