Visual RFC.
ALL RFCs / RFC 9990
Read the RFC ↗
RFC 9990 / CURRENT DMARC

Delivery and duplicates

04

A retried report must retain its identity so the recipient can recognize duplicate information.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

RFC 9990 · § 3.5.4EXAMPLE
3 / 3
Delivery and duplicatesA retried report must retain its identity so the recipient can recognize duplicate information.Delivery and duplicatesreport_id: R42interval: begin … endfirst R42retry R42Recognize duplicate observations
03
Detect duplicate data

The consumer avoids blindly treating a retry as new observations.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Use the same unique identifiers when retrying the same report.

  • Use the same unique identifiers when retrying the same report.
  • Receiver policy determines how to handle duplicate reports or overlapping information.
  • Malformed delivery URIs should be ignored under the delivery rules.
DETAILS

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
All chapters in this RFC
  1. Aggregate counts into rows
  2. XML report anatomy
  3. Request and recipient consent
  4. Delivery and duplicates
  5. Privacy and untrusted reports
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗