I think some clarification is in order regarding the removal of the ability to specify a maximum report size in the DMARC URI.
2.5 Transport Any reporting URI that includes a size limitation exceeded by the generated report (after compression and after any encoding required by the particular transport mechanism) MUST NOT be used. There may be existing DMARC Policy Records that includes a size limitation, but it is not discussed here at all. If this iteration is to fully obsolete RFC 7489, I think it could be considered a BC break not to mention the obsolete size parameter of "rua" tags. The same section goes on: [If shit really hits the fan] the Mail Receiver MAY send a short report indicating that a report is available but could not be sent. I'm sure this does not suggest that a minimal aggregate report should be sent indicating that a "real" but too big aggregate report is available. As a minimum the first 'report' could be turned into 'message' to avoid any confusion. Artart review may have pointed this out, but I didn't catch it at the time. Moreover, the only size limitation is the one that can be discovered in the SMTP transaction from the SMTP SIZE extension (RFC 1870). Are we trying to suggest that if the Reporting organization, at EHLO time, discover that the size of the Report message exceeds the limit, it should switch to sending an alternative message notifying the recipient that their SIZE declaration does not allow them to receive their report? That sounds quite complicated. Daniel K. _______________________________________________ dmarc mailing list -- [email protected] To unsubscribe send an email to [email protected]
