You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DMARC policy in the rego is based purely on DNS. Looking at Agency 2 and Agency 1's data, the DNS results are not being correctly populated for a subset of their domains, perhaps due to transient errors.
I believe the appropriate fix for this issue is better retry logic for DMARC. I am retitling the bug as soon and unassigning from me for prioritization of implementation in Dolphin (or deferral to later release).
gdasher
changed the title
Agency 2 Pilot: EXO 2.4; DMARC Failures
Implement better DNS Retry logic (Agency 2 Pilot: EXO 2.4; DMARC Failures)
Feb 2, 2023
Specifically, on transient DNS failures, we should retry as well as differentiate this error condition from NXDOMAIN. Logic should cover all policies reliant on DNS data (DMARC, SPF, DKIM).
Agency 2 manages their DMARC policy outside of EXO but could still verify they meet the policy via DNS lookups. We should investigate why they failed.
The text was updated successfully, but these errors were encountered: