On Fri, 11 Dec 2020, Brotman, Alex wrote:
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.
The goal was to clarify the language, without (to the best of our ability)
changing the schema. I'd welcome a other attempts at clarifications (if you
believe mine introduces structural XML changes).
So it'd say yeah, we know the XML lets you put multiple header_from
domains in the same report row, but please don't do that, send a separate
report row for each header_from?
I suppose that could work.
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>
Regards,
John Levine, [email protected], Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
