DMARC passes when at least one supported authentication path both passes and aligns with the visible From domain. A message can therefore have a passing SPF result yet fail DMARC if the authenticated domain belongs to an unrelated service.
Required for AuthSMTP domain authorisation
Before a customer-owned sending domain can be authorised, it must publish one valid SPF record covering AuthSMTP and every other legitimate sender, publish a valid DMARC record, and have its AuthSMTP DKIM configuration published and verified. p=none is acceptable as a starting monitoring policy; the domain does not need to begin at quarantine or reject. The longer-term plan should be to review reports, correct authentication and alignment for every legitimate sender, then progress to p=quarantine and ultimately p=reject.
AuthSMTP deliberately requires all three authentication configurations even though one aligned authentication path can satisfy DMARC's technical pass condition. Mailbox-provider requirements are becoming stricter, and customers may already send—or later grow to send—high volumes. Verified domain-specific DKIM cryptographically identifies genuine AuthSMTP mail, while DMARC relates authentication to the visible From domain and provides reporting and policy controls. Together with SPF, they improve trust and reduce the risk of successful domain spoofing or impersonation.
Move from visibility to enforcement
- List every service that sends using the domain.
- Configure aligned DKIM wherever possible.
- Publish a valid reporting address and protect it from overload.
- Review aggregate reports for genuine and unauthorised sources.
- Correct gaps before progressing from
p=noneto quarantine or reject. - Continue monitoring after enforcement.
DMARC is not a one-time DNS switch. New suppliers, forgotten applications and forwarding paths can change the results, so policy must be accompanied by ownership and regular review.
See our DMARC guide for syntax and AuthSMTP considerations.
Inventory all legitimate senders, begin with monitored reporting and enforce only after alignment gaps are resolved.
Review a recent DMARC aggregate report and account for every source sending mail that uses your visible From domain.