On Sat 16/May/2020 20:45:43 +0200 Seth Blank wrote: > On Fri, May 15, 2020 at 7:20 PM John Levine <[email protected]> wrote: >> In article >> <cal0qlwaskzdyeqnjs-bj4ttfdgevfc8gaukmvnost0wj3ge...@mail.gmail.com> you >> write: >>> +1, unless there are known cases where the XML payload size is a problem >>> that switching to JSON would solve. >> >> It's gzipped, do I doubt it would make much difference. Gzip is really >> good at compressing the boilerplate strings that make XML bigger than >> JSON. >> >> Also, FWIW, in seven years the largest report message I ever got was >> under 300K, and if people really are concerned about big reports, I >> would much rather revive https reporting which avoids base64 encoding >> and doesn't have to buffer copies of the report for relay. >> > > Hatless, as a data point: at Valimail we see reports that are hundreds of > megabytes in size, and sometimes push close to a gigabyte. These reports > continue to increase in size month over month as sending volume, geographic > footprint, deployed third party services, and fraudulent mail attempting to > impersonate the domain continually increase
Another way to halve the size of the reports is to halve the reporting interval. I think this can be made clearer in DMARCbis, so I added ticket #71. Best Ale -- _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
