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
I believe you, but switching to JSON would not make any difference. The
reports are gzipped and the extra verbiage of XML is all squeezed out in
the compression. I have a 4.1 meg XML report that zipped to 136K, about
3% of the original size, which I think is a typical ratio for reports of
any size.
E-mail is a lousy way to send around gigabyte files, so we should make
https work. Semantically HTTP PUT is the right way to do it but HTTP POST
like mta-sts does would be OK. It uploads a binary application/gzip
version of the report so it's about as efficient as it can be.
R's,
John
PS: Another think we might consider, although it would be significant
work, is to add application/bzip2 as a compression type. That 4.1M XML
file crunches down to 51K as bzip2. It has some issues, it's not well
documented other than by the reference implementation, and it'd be yet
another way for things not to interoperate so we'd have to add a signal in
the DMARC record to say that reports can use it.
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
