RFC 7489, "Domain-based Message Authentication, Reporting, and Conformance (DMARC)", March 2015
Source of RFC: INDEPENDENT
⚠ This RFC has been obsoleted!
Obsoleted by: RFC9989, RFC9990, RFC9991
Updated by: RFC8553, RFC8616
Errata-ID: 7099
- Status:
- Held for Document Update
- Type:
- Technical
- Reported By:
- Cris van Pelt
- Date Reported:
- 2018-05-28
- Held for Document Update by:
- Eliot Lear
- Date Held for Document Update:
- 2024-12-03
Section 7.2.1.1 says:
The extension MUST be "xml" for a plain XML file, or "xml.gz" for an
XML file compressed using GZIP.
"unique-id" allows an optional unique ID generated by the Mail
Receiver to distinguish among multiple reports generated
simultaneously by different sources within the same Domain Owner.
For example, this is a possible filename for the gzip file of a
report to the Domain Owner "example.com" from the Mail Receiver
"mail.receiver.example":
mail.receiver.example!example.com!1013662812!1013749130.gz
It should say:
The extension MUST be "xml" for a plain XML file, or "xml.gz" for an
XML file compressed using GZIP.
"unique-id" allows an optional unique ID generated by the Mail
Receiver to distinguish among multiple reports generated
simultaneously by different sources within the same Domain Owner.
For example, this is a possible filename for the gzip file of a
report to the Domain Owner "example.com" from the Mail Receiver
"mail.receiver.example":
mail.receiver.example!example.com!1013662812!1013749130.xml.gz
Notes:
The example filename uses an invalid extension (not one of "xml", "xml.gz").