Knowledge base
Forwarding and mailing lists
Why forwarded mail often fails SPF, when it fails DMARC, and what ARC does about it.
Forwarding is the most common reason legitimate mail fails DMARC, and the most common reason people worry about enforcing it.
Why forwarding breaks SPF
When a message is forwarded, for example from a university address to a personal Gmail account, the forwarding server sends it on. The receiver sees the forwarder's IP address, which is not in your SPF record, so SPF fails.
Why DKIM usually survives
A plain forward does not change the message, so your DKIM signature stays valid and DMARC still passes. This is why DKIM signing with your own domain matters so much.
Mailing lists
Mailing lists often change messages: adding a footer, or "[List name]" in the subject. That breaks the DKIM signature, and SPF fails too, so DMARC fails. Modern list software works around this by rewriting the From address to the list's own domain.
ARC
ARC (Authenticated Received Chain) lets intermediaries such as forwarders and lists record the authentication results they saw before they changed anything, and sign that record. Receivers that trust the intermediary, including the big mailbox providers, can use it to accept the message despite the DMARC failure. Reports may show this as a forwarded or trusted_forwarder override.
What to do
- Make sure every legitimate service signs with DKIM using your domain.
- Expect a small amount of forwarded mail to fail. In reports it typically shows as DKIM pass, SPF fail, from IPs belonging to mail providers.
- Do not add forwarders to your SPF record. It does not help and wastes lookups.
See it on your own domain.
Check your DMARC, SPF and DKIM setup in seconds, then let us watch your reports for you.
Start free