Isn't the override in the RowType? So you can just have multiple RecordTypes, each with different RowTypes?
Ultimately, it seems like the report is a bunch of fields with a count, and so the composition is to make sure that the set of rows is a "unique" key. Theoretically you should log even the published policy at eval time, so you can report different counts even if the policy changes over that period... even if you'd have to send separate reports. The schema doesn't really make that clear, to my mind, I wouldn't have buried the count. Brandon On Tue, Jan 28, 2020 at 5:26 AM Brotman, Alex via dmarc-discuss < dmarc-discuss@dmarc.org> wrote: > What is to be done if only a portion of the messages from the reporting > period receive a policy override? Perhaps this is done based on IP, or > only applied part way through the day. It seems like in the specification, > the reporting definition assumes the entire set of reported messages has > the override. > > -- > Alex Brotman > Sr. Engineer, Anti-Abuse & Messaging Policy > Comcast > > > _______________________________________________ > dmarc-discuss mailing list > dmarc-discuss@dmarc.org > http://www.dmarc.org/mailman/listinfo/dmarc-discuss > > NOTE: Participating in this list means you agree to the DMARC Note Well > terms (http://www.dmarc.org/note_well.html) >
_______________________________________________ dmarc-discuss mailing list dmarc-discuss@dmarc.org http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
