TL;DR: DMARC only reduces impersonation risk when every legitimate sender stays inventoried, aligned and governed, according to Valimail. DMARC enforcement depends on keeping sender records current so quarantine and reject do not break valid mail.
Editorial analysis by NHI Mgmt Group, based on content published by Valimail: “DMARC implementation: How to protect your domain in 6 steps”.
Key questions
Q: Why can a legitimate email still fail DMARC even when SPF and DKIM both pass?
A: DMARC only counts SPF or DKIM when the authenticated domain aligns with the domain shown in the From header.
Q: What are common mistakes with DMARC Policy?
A: Common DMARC Policy mistakes are publishing policy before SPF and DKIM alignment is working, moving too quickly to reject, and forgetting to monitor reports for legitimate senders that fail authentication.
Q: How should security teams roll out SPF, DKIM, and DMARC without breaking legitimate email delivery?
A: Start by inventorying every system that sends mail on behalf of the domain, then publish SPF and DKIM for those senders before moving DMARC from monitor mode to enforcement.
Practitioner guidance
- Document every authorized sender Build and maintain a complete inventory of mail servers, SaaS platforms, notification services and subdomains that send on behalf of the domain.
- Publish SPF with explicit sender scope List only approved IPs and sending domains, then use the strictest qualifier that will not break legitimate mail after testing.
- Deploy DKIM per sender and subdomain Generate separate signing keys for each service that sends mail so delegated systems can be rotated or removed without affecting the rest of the estate.
Bottom line: DMARC only reduces impersonation risk when every legitimate sender is inventoried, aligned and continuously governed.
Glossary terms: DMARC, SPF, DKIM, Identifier Alignment
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
DMARC is really a sender identity governance problem, not just an email authentication problem. The article shows that the hard part is not publishing a record, but maintaining control over every authorised mail source as marketing, cloud and SaaS systems change. That is an identity lifecycle issue in disguise, because the trust boundary is the set of systems allowed to speak for the domain.
A question worth separating out:
Q: Should organisations treat third-party mail services as part of identity governance?
A: Yes. Any system that sends mail on behalf of your domain is exercising delegated identity, even if it is a marketing platform, CRM or cloud service. Those senders need ownership, lifecycle control and removal procedures just like other delegated access paths, or they become persistent trust assumptions.
👉 Read our full editorial: DMARC implementation still fails without disciplined SPF and DKIM governance