Opened 3 years ago

Closed 16 months ago

#43 closed defect (fixed)

Subdomain reporting clarity

Reported by: seth@… Owned by: alex_brotman@…
Priority: major Milestone: Deliverable #3 (changes to DMARC base spec + DMARC Usage Guide
Component: dmarc-aggregate-reporting Version:
Severity: - Keywords: clarify reports


The spec appears to be unclear on how subdomains are to be reported - ie
most but not all implementations have performed this as intended, in the
same XML as the top level domain (when the subdomain does not have its
own DMARC TXT record)


Change History (5)

comment:1 Changed 3 years ago by seth@…

  • Component changed from rfc7601bis to dmarc-bis
  • Owner draft-ietf-dmarc-rfc7601bis@… deleted
  • Status changed from new to assigned

comment:2 Changed 2 years ago by alex_brotman@…

  • Owner set to alex_brotman@…
  • Status changed from assigned to new

comment:3 Changed 2 years ago by todd.herr@…

  • Component changed from dmarc-bis to dmarc-aggregate-reporting

comment:4 Changed 20 months ago by alex_brotman@…

This exists in -01. I'd be okay extracting that into its own section with a normative MUST if others feel it appropriate.

The report SHOULD include the following data:

  • The DMARC policy discovered and applied, if any
  • The selected message disposition
  • The identifier evaluated by SPF and the SPF result, if any
  • The identifier evaluated by DKIM and the DKIM result, if any
  • For both DKIM and SPF, an indication of whether the identifier was

in alignment

  • A separate report should be generated for each 5322.From

subdomain, regardless of which policy domain was used during
receipt of messages

  • Sending and receiving domains
  • The policy requested by the Domain Owner and the policy actually

applied (if different)

  • The number of successful authentications
  • The counts of messages based on all messages received, even if

their delivery is ultimately blocked by other filtering agents

comment:5 Changed 16 months ago by alex_brotman@…

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.