In article
<mn2pr11mb43510f27a700c9644f9baed4f7...@mn2pr11mb4351.namprd11.prod.outlook.com>
you write:
>Based on a discussion from last year
>(https://mailarchive.ietf.org/arch/msg/dmarc/YoHhhaAfwRjbd8aq4fiV6xU1ifw/),
>there was a
>request/ticket to clarify the language in the document.
>
>>From https://tools.ietf.org/html/rfc7489#section-7.2:
>
> * Data for each Domain Owner's subdomain separately from mail from
> the sender's Organizational Domain, even if there is no explicit
> subdomain policy
That would be a change to the XML report schema. It'd change as I show
below to force a separate row for each header_from.
That's a somewhat incompatible change, so I'd want to be sure we agree
that it's a real problem that's worth changing the report format. I
suppose if we do we should encourage report consumers to be prepared
for old and new formats.
R's,
John
<xs:complexType name="IdentifierType">
<xs:all>
<!-- The envelope recipient domain. -->
<xs:element name="envelope_to" type="xs:string"
minOccurs="0"/>
<!-- The RFC5321.MailFrom domain. -->
<xs:element name="envelope_from" type="xs:string"
minOccurs="1"/>
Old:
<!-- The RFC5322.From domain. -->
<xs:element name="header_from" type="xs:string"
minOccurs="1"/>
New:
<!-- The RFC5322.From domain. -->
<xs:element name="header_from" type="xs:string"/>
</xs:all>
</xs:complexType>
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
