What DMARC adds to SPF and DKIM
SPF and DKIM answer different questions about an email. SPF checks whether the sending server is authorized by the domain used for the message’s envelope sender, also called the return-path domain. DKIM checks a cryptographic signature associated with a domain named in the signature’s d= value. Neither test, by itself, requires that domain to match the From address a reader sees in their mail app.
DMARC connects authentication to that visible From address. A message passes DMARC when at least one of two things is true: SPF passes and its authenticated domain aligns with the From domain, or DKIM passes and its signing domain aligns with the From domain. Both paths do not have to pass. But a passing result for an unrelated domain does not establish DMARC alignment.
Why a passing result can still be misaligned
Imagine a message whose visible From address is notices@example.com. A delivery service sends it using a return-path address at mailer-service.example.net. The service may be fully authorized to send for example.net, so SPF passes. Yet that SPF result does not align with example.com. If the service also signs the message with DKIM using d=mailer-service.example.net, that signature may pass too, but it is still not aligned. With no aligned passing result, the message fails DMARC.
This does not automatically mean the delivery service is untrustworthy. It means its authentication, as configured for that message, does not prove a connection to the domain in the visible From address. To establish that connection, the domain owner might configure a service-supported return-path domain under example.com, a DKIM signature using example.com or an aligned subdomain, or both. The available options depend on how the service handles outgoing mail.
Relaxed and strict alignment
By default, DMARC uses relaxed alignment. Under relaxed alignment, a subdomain can align with its parent organizational domain. For example, if the From domain is example.com, an SPF-authenticated domain of bounce.example.com or a passing DKIM signature with d=mail.example.com can align. The authentication test itself must still pass; a similar-looking domain name cannot make a failed SPF check or broken DKIM signature valid.
Strict alignment requires an exact domain match. With a From address at example.com, a result for mail.example.com would not align under strict rules. A DMARC record can request strict SPF alignment with aspf=s, strict DKIM alignment with adkim=s, or both. Before using either setting, consider how your legitimate senders use subdomains. Strict alignment can be useful for a deliberate domain setup, but it can also cause otherwise legitimate messages to fail DMARC.
What forwarding and mailing lists can change
Forwarding illustrates why DMARC offers two paths to a pass. When a message is forwarded, the forwarding server’s IP address may not be authorized by the original envelope sender’s SPF record. SPF can therefore fail at the final destination even though it passed when the message was first sent. If the original DKIM signature remains valid and aligned, the message can still pass DMARC.
A mailing list may present a different challenge. If it changes the subject or message body, an original DKIM signature may no longer verify. If the list also sends with its own envelope domain, SPF might pass for the list while remaining unaligned with the original From domain. List operators and receiving systems may handle these cases in different ways. When investigating a failure, examine the specific message path rather than assuming every failure has the same cause.
A practical way to troubleshoot alignment
Start with a legitimate message sent through each platform your domain uses, such as your regular mail provider, a contact-form service or a newsletter tool. In the received message’s authentication results, identify the visible From domain, the domain SPF authenticated and the DKIM d= domain for each passing signature. Compare each authenticated domain with the From domain under your DMARC alignment settings. Authentication-result headers are useful clues, but they should be read in the context of the receiving system that added them.
If neither passing result aligns, check the sender’s documented options for a custom return-path domain and domain-specific DKIM signing. Make changes in the sender’s settings and DNS as a coordinated setup; simply adding an SPF entry to your domain does not make a service’s unrelated return-path domain align. Test again after configuration changes, and account for normal DNS propagation and cached records.
DMARC policies such as p=none, p=quarantine and p=reject tell receivers how the domain owner wants messages that fail DMARC handled, although receiver behavior may vary. A monitoring policy can help you identify legitimate senders before asking receivers to treat failures more aggressively. The goal is not to make every message pass both SPF and DKIM. It is to ensure legitimate mail has at least one reliable, aligned path to a DMARC pass.



