Re: [dmarc-ietf] Report bombing is a prolem, Forensic report loops are not

[John Levine <[e-mail]>]

In article <[e-mail]> you write:
>Rate limiting usually implies a number of buckets.  They are managed by 
>imposing limits per time periods, which can be either server-global or per 
>bucket.  Normally, for MSA usage, one has one bucket per user.  I have never 
>implemented failure reporting, but I'd guess buckets may vary.  Besides the 
>signing domain (which determines the report consumer), the receiving address, 
>the sender and the spam flag may deserve their own buckets.

The only one that matters for DMARC reporting is the recipient
address, since the purpose of rate limiting is to avoid overloading
the recipient mail system. I wouldn't worry about trying to send a
"representative" set of reports.

Keep in mind that very few people send failure reports at all. In my
experience few of them are useful. Most of mine are ordinary mailing
list messages where the failure is not surprising and does not mean
that anything needs to be fixed.

R's,
John