Hi,
the last two paragraphs of section 4.1 also show a neat asymmetry between
rua and ruf. The first sounds like the notification that feedback exists
rather than something a mail receiver should do. The second is good, but
not normative.
OLD
DMARC's feedback component involves the collection of information
about received messages claiming to be from the Author Domain for
periodic aggregate reports to the Domain Owner or PSO. The
parameters and format for such reports are discussed in
[I-D.ietf-dmarc-aggregate-reporting]
A DMARC-enabled Mail Receiver might also generate per-message reports
that contain information related to individual messages that fail
authentication checks. Per-message failure reports are a useful
source of information when debugging deployments (if messages can be
determined to be legitimate even though failing authentication) or in
analyzing attacks. The capability for such services is enabled by
DMARC but defined in other referenced material such as [RFC6591] and
[I-D.ietf-dmarc-failure-reporting]
NEW
A DMARC-enabled Mail Receiver SHOULD collect authentication results
and generate aggregate reports that contain information about
received messages claiming to be from the Author Domain for periodic
aggregate reports to the Domain Owner or PSO. The parameters and
format for such reports are discussed in
[I-D.ietf-dmarc-aggregate-reporting]
A DMARC-enabled Mail Receiver MAY also generate per-message reports
that contain information related to individual messages that fail
authentication checks. Per-message failure reports are a useful
source of information when debugging deployments (if messages can be
determined to be legitimate even though failing authentication) or in
analyzing attacks. The capability for such services is enabled by
DMARC but defined in other referenced material such as [RFC6591] and
[I-D.ietf-dmarc-failure-reporting]
How's that?
Best
Ale
--
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
