An individual failure report
01A failure report concerns an individual message, unlike an aggregate traffic summary.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 2 ↗
RFC 9991 · § 2EXAMPLE
3 / 3
03
Choose whether to report
Apply reporting requests, operational limits, and privacy policy.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
RFC 7489DMARC failure reports
Failure reporting is separated from RFC 7489 into its own specification. It also updates RFC 6591’s reporting format and gives explicit privacy guidance for deployment.
Read the updated RFC section ↗Reports normally follow detection quickly rather than waiting for an aggregate interval.
- Reports normally follow detection quickly rather than waiting for an aggregate interval.
- Message headers or content can support diagnosis, subject to privacy policy.
- A requested failure report is not guaranteed: operators may limit or disable generation.
Examples are illustrative. Read the exact policy, reporting, and privacy rules in the linked current specification.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy