A DMARC record's RUA target may specify a maximum report size accepted at the target URI. The reporting code should be aware of this and minimally strip the option before attempting to make use of the URI or URI-domain. A more complete solution obviously would make use of the data in the option.
Question:
do you consider+enforce the rua size limitation flag, such as provided by "rua=mailto:dmarc@tomki.com!25m”? Do you enforce an alternate maximum?
or do you ignore it?
or do records with this option fail?
because the code would extract the email address as dmarc@tomki.com!25m which is an address with a domain tomki.com!25m not related to the organizational domain or from _report._dmarc….
It would fail only for the email addresses that are set like this.
A DMARC record's RUA target may specify a maximum report size accepted at the target URI. The reporting code should be aware of this and minimally strip the option before attempting to make use of the URI or URI-domain. A more complete solution obviously would make use of the data in the option.
Question: do you consider+enforce the rua size limitation flag, such as provided by "rua=mailto:dmarc@tomki.com!25m”? Do you enforce an alternate maximum? or do you ignore it? or do records with this option fail?
Answer from Franck: I ignore it
and I think it would fail at the moment https://github.com/linkedin/dmarc-msys/blob/master/dmarc_report.py#L85
because the code would extract the email address as dmarc@tomki.com!25m which is an address with a domain tomki.com!25m not related to the organizational domain or from _report._dmarc….
It would fail only for the email addresses that are set like this.