Topic · Authentication
SPF pass without DMARC alignment
SPF may pass while contributing nothing to DMARC if the authenticated envelope domain differs from the visible From domain.
How it works
The SPF result is evaluated first; DMARC separately compares the authenticated domain against the message's RFC 5322 From domain.
What can go wrong
Dashboards that display only SPF pass can overlook forgery or third-party misalignment.
What to check or do
Check the smtp.mailfrom and header.from identities and configure a suitable aligned return-path or DKIM signature.
Practical scenario
A billing platform sends receipts with From: [email protected], but MAIL FROM is [email protected]. SPF passes for esp.example while DMARC still fails because its authenticated domain does not align. The problem is identity alignment, not simply missing SPF IP addresses.
Verification checklist
- Capture the actual recipient-side Authentication-Results header.
- Find smtp.mailfrom, header.from and any valid DKIM d= identifiers.
- Configure an aligned bounce domain or first-party DKIM signing with the ESP.
- Retest multiple messages and review aggregate reports for pass trends.
How to investigate SPF pass without DMARC alignment
- Signal to investigate
- A campaign uses the vendor's return-path, passes SPF, then fails DMARC under the customer's From.
- Evidence to collect
- Record smtp.mailfrom and header.from from the same real delivered message.
- Common wrong conclusion
- A screenshot stating SPF=pass can be misleading if the authenticated domain is not visible.
How to interpret the evidence
When From: invoices.example.com is visible but the vendor authenticates MAIL FROM: returns.vendor.example, the SPF pass validates the vendor's envelope domain. Unless another passing, aligned DKIM signature exists, the message will not pass DMARC on SPF alone. This is a common reason a sender insists SPF is working while users still receive policy rejections.
What to change and how to verify it
Test messages at the actual destination mailbox and read trusted Authentication-Results fields. Enable aligned custom return-path or DKIM signing where supported. Do not add more SPF includes to the visible From domain as a substitute for fixing the wrong envelope identity.
# Inspect a delivered raw header for:
# header.from=, smtp.mailfrom=, header.d=Educational example; not validated against your live infrastructure.Put this into practice
Run a focused check, then explore protection if your domain needs it.