https://datatracker.ietf.org/doc/html/rfc7489<!-- Taking into account everything else in the record, the results of applying DMARC. -->
<xs:complexType name="PolicyEvaluatedType">
<xs:sequence>
<xs:element name="disposition" type="DispositionType"/>
<xs:element name="dkim" type="DMARCResultType"/>
<xs:element name="spf" type="DMARCResultType"/>
<xs:element name="
reason" type="PolicyOverrideReason" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<!-- How do we allow report generators to include new classes of override reasons if they want to be more specific than "other"? -->
<xs:complexType name="PolicyOverrideReason">
<xs:all>
<xs:element name="
type" type="PolicyOverrideType"/>
<xs:element name="
comment" type="xs:string"minOccurs="0"/>
</xs:all>
</xs:complexType>
<!-- Reasons that may affect DMARC disposition or execution thereof. -->
<xs:simpleType name="PolicyOverrideType">
<xs:restriction base="xs:string">
<xs:enumeration value="forwarded"/>
<xs:enumeration value="sampled_out"/>
<xs:enumeration value="trusted_forwarder"/>
<xs:enumeration value="mailing_list"/>
<xs:enumeration value="
local_policy"/>
<xs:enumeration value="other"/>
</xs:restriction>
</xs:simpleType>
Par vysvetlivek:
https://powerdmarc.com/dmarc-policy-overrides/https://mxtoolbox.com/dmarc/details/dmarc-policy-override-types