TL;DR: Forwarded mail can fail SPF even when it is legitimate, because forwarding changes the evaluated sending IP, with Valimail noting the mismatch. DMARC then depends on aligned signing and limited downstream modification, not SPF alone.
Editorial analysis by NHI Mgmt Group, based on content published by Valimail: “Why forwarded emails break SPF (and how DKIM solves it)”.
Key questions
Q: When should organisations rely on DKIM instead of SPF for forwarded mail?
A: Use DKIM as the primary success signal when forwarding, mailing lists or relays are part of normal mail flow.
Q: What are the warning signs that email authentication is misaligned with forwarding?
A: Common signs include DMARC failures on otherwise expected mail, SPF failures that only appear after messages pass through a forwarder, and DKIM failures tied to disclaimers, footers or gateway rewriting.
Q: Why does forwarded email fail SPF even when the message is legitimate?
A: SPF checks the IP address of the server that delivers the message at the recipient boundary.
Practitioner guidance
- Validate forwarding-heavy mail flows separately Test mailbox forwarding, mailing lists and gateway relays as distinct delivery paths so you can see where SPF fails and whether DKIM still aligns.
- Keep SPF limited to authorised senders Avoid adding arbitrary forwarding services to SPF records, because that expands the set of systems allowed to send for the domain and weakens spoofing resistance.
- Prioritise DKIM alignment for forwarded mail Sign the visible From domain and the headers that DMARC depends on, then review any downstream system that modifies bodies, headers or routing.
Bottom line: Forwarding breaks SPF because the evaluated sending IP changes, not because the message is necessarily fraudulent.
Glossary terms: Sender Policy Framework, DomainKeys Identified Mail, DMARC, Sender Rewriting Scheme
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Forwarding exposes the weakness of path-based trust: SPF assumes the sending server at evaluation time is the one the domain intended, but forwarding inserts a new server that breaks that assumption. That makes SPF useful for direct spoofing control and weak for email distribution patterns that reshape delivery after the sender has finished. Practitioners should treat forwarding as a design condition, not an exception.
A question worth separating out:
Q: Should teams rewrite SPF policy or fix the forwarding path when DMARC starts failing?
A: Fix the forwarding path first. Broadening SPF to cover every possible forwarder usually increases the authorised sender set and creates maintenance problems. A better approach is to keep SPF scoped to real sending infrastructure, preserve DKIM alignment for the visible From domain, and use DMARC reports to pinpoint where forwarding is changing authentication results.
👉 Read our full editorial: Forwarded email often breaks SPF but DKIM still holds