It appears that Mark Alley <mark.al...@tekmarc.com> said: >-=-=-=-=-=- > >This may have been thought of before, so forgive the potentially >duplicate idea, I was musing earlier about feedback reporting based on a >percent of the overall mail per-source. I'm thinking of something >similar in concept to the pct= tag for published policy.
I don't understand what problem that would solve. If you're going to go through the effort of evaluating DMARC alignment for incoming mail, the incremental effort to save the result in a database is small, and saving only some of the results wouldn't make it any easier. I can say this from experience having written the code. Once you have the info in the database, generating aggregate reports is a straightforward data dump and format. I suppose that if you ran a very large mail system there might be some issues if the reports got too big to mail, but I get regular reports from giant mail systems including Google, Yahoo, and Comcast so we know it's not a problem in practice. There's a separate issue with failure reports. Hypothetically, if someone did a giant spam run using your address, you might get indirectly mailbombed with failure reports. But I can say from experience, having been collecting failure reports for a decade, some of my addresses are heavily forged, hardly anyone sends the reports, and it's not a problem. R's, John _______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
