TLS-RPT reports missing
TLS reporting destinations are not receiving reports.
Problem summary
TLS reporting destinations are not receiving reports.
Symptoms
- _smtp._tls TXT present but no TLS reports arrive
- rua mailbox empty for TLS-RPT
- External TLS report processor shows no data
Possible causes
- Wrong rua mailto/https destination
- Low failure volume — few reports expected
- Mailbox filtering or analyzer misconfiguration
How to diagnose
- Confirm _smtp._tls TXT rua targets
- Check spam folders and analyzer auth for the domain
- Generate a controlled TLS failure in testing if safe to do so
How to fix
- Fix rua targets (example shape): v=TLSRPTv1; rua=mailto:tls-reports@example.com
- Authorize external processors per their docs
- Ensure the destination can accept report volume
How to verify
- At least one TLS report received after real or test failure events
- Report destination remains monitored
Prevention
- Monitor TLS-RPT freshness alongside DMARC rua
- Re-check after mail host or DNS migrations
When to escalate
- Production mail is failing for a material share of recipients after remediation attempts