The question then is - how does a report receiver interpret the multiple SPF results? A row has only a single auth message count; if there are three SPF rows, then which SPF result goes with how many messages? It's ambiguous (not to mention hard to render to an end user).
If an IP has multiple auth result combinations, shouldn't it have one row per combination so that the report receiver can get an accurate idea of how many instances of each combination are being reported? -- Les Barstow On Wed, Mar 16, 2016 at 8:27 AM, Elizabeth Zwicky <[email protected]> wrote: > > Rows are defined by IP; if the same IP uses multiple MAILFROM and SPF is > bounded what is the reporter supposed to do? Duplicate rows? > > Limiting SPF changes the row key in bad ways. (Unless all senders are > well-behaved in ways they are not required to be.) > > Elizabeth > > [email protected] > > On Mar 15, 2016, at 4:10 PM, Franck Martin <[email protected]> wrote: > > > > > > > ------------------------------ > > *From: *"Tomki" <[email protected]> > *To: *"dmarc" <[email protected]> > *Sent: *Tuesday, March 15, 2016 3:27:15 PM > *Subject: *[dmarc-ietf] SPFAuthResultType unbounded > > Does it make sense that SPFAuthResultType element counts are allowed to be > unbounded? > I would think that it should be a maximum of 2, and then only if the scope is > indicated (helo/mfrom) > > from https://tools.ietf.org/html/rfc7489 > > <xs:complexType name="AuthResultType"> > <xs:sequence> > <!-- There may be no DKIM signatures, or multiple DKIM > signatures. --> > <xs:element name="dkim" type="DKIMAuthResultType" > minOccurs="0" maxOccurs="unbounded"/> > <!-- There will always be at least one SPF result. --> > <xs:element name="spf" type="SPFAuthResultType" minOccurs="1" > maxOccurs="unbounded"/> > </xs:sequence> > </xs:complexType> > > > > Makes sense, does it matter? > > _______________________________________________ > dmarc mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dmarc > > > _______________________________________________ > dmarc mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dmarc > >
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
