In article <1675430.NNnUSil6oV@kitterma-e6430> you write:
>As an example, I have been able to find four messages I sent to
>lists.debian.org email lists on April 30th. The volume reported for that
>source for that day from various feedback reporters was 2,436. This makes it
>a little hard to
On Fri 04/May/2018 21:37:35 +0200 Scott Kitterman via dmarc-discuss wrote:
>
> 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? [my emphasis]
The
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
Would this really help?
You haven't explained what you mean by "a little hard to consume". On
the face of it, it's just an integer; a 1 is no easier to perform
arithmetic on than a 2,436. If what you mean is that it's difficult to
make meaningful comparison between the number that you send
I participate in a lot of mailing lists many of which that have a large number
of subscribers. As a result, when I send a single message to a mailing list,
many copies of the same message get sent to users at large mail providers.
These get counted as individual messages in aggregate
