Some rua= and ruf= destinations are persistently dead, rate-limited, or otherwise unable to accept DMARC reports (e.g. a Gmail inbox published as a reporting address for a high-volume sender). Currently there is no way to suppress delivery to these destinations short of modifying the database or source code.
This issue tracks adding a NoReportsList config option pointing to a flat file of domains or addresses to skip when sending aggregate or failure reports -- similar in pattern to IgnoreHosts. An admin could add a known-bad destination to the file and report delivery to that address would be suppressed without affecting other destinations.
The skip list would need to be honored in two places:
opendmarc-reports (Perl), checked before SMTP or HTTP delivery
- The milter itself, checked before
popen() for RUF failure reports
Some rua= and ruf= destinations are persistently dead, rate-limited, or otherwise unable to accept DMARC reports (e.g. a Gmail inbox published as a reporting address for a high-volume sender). Currently there is no way to suppress delivery to these destinations short of modifying the database or source code.
This issue tracks adding a
NoReportsListconfig option pointing to a flat file of domains or addresses to skip when sending aggregate or failure reports -- similar in pattern toIgnoreHosts. An admin could add a known-bad destination to the file and report delivery to that address would be suppressed without affecting other destinations.The skip list would need to be honored in two places:
opendmarc-reports(Perl), checked before SMTP or HTTP deliverypopen()for RUF failure reports