On 05/04/2018 12:37 PM, Scott Kitterman via dmarc-discuss wrote:
I participate in a lot of mailing lists many of which that have a large number
of subscribers. ...
Shouldn't it be possible to de-duplicate these based on message ID before
sending aggregate reports back? Can/should this be added to DMARC the next
time the specification is updated?
There may be interesting anti-abuse cases that justify storing this kind
of information in a readily accessible form for e.g. de-duplication,
versus a static log file.
But even if receivers / mailbox providers are already doing that,
where's their incentive for the reporting change you describe? What
would be the resulting improvement in the quality of mailstreams sent
using a given domain? The reduction in customer support, or increase in
customer satisfaction, of the kind they purportedly see when it's easier
to detect fraudulent messages?
I can understand how the reporting change you suggest *might* be useful
to the individual sender, where the sender and the domain operator total
1 or 2. Can you help us understand what's in it for the other parties
involved? And how does it help in the more typical case where there are
between dozens and thousands of users of the domain?
--S.
_______________________________________________
dmarc-discuss mailing list
dmarc-discuss@dmarc.org
http://www.dmarc.org/mailman/listinfo/dmarc-discuss
NOTE: Participating in this list means you agree to the DMARC Note Well terms
(http://www.dmarc.org/note_well.html)
