Skip to content
  • There are no suggestions because the search field is empty.

Forwarded mail fails DMARC

Forwarded mail usually fails SPF, because the next server sees the forwarder's IP address, not yours. That alone doesn't fail DMARC. If your message carries a DKIM signature aligned with your From domain and the forwarder doesn't change the message, DKIM still passes and so does DMARC. Forwarded mail fails DMARC when both break: SPF because of the new path, and DKIM because a list, gateway, or forwarder edited the message. So the fix that's in your hands is aligned DKIM on every stream. Some receivers can also accept the mail anyway through ARC, if they choose to trust the forwarder.

How to tell it's forwarding

Forwarding has a recognizable pattern, both in reports and in headers.

In aggregate reports (A field-by-field walk-through of a DMARC aggregate report):

  • The source IP belongs to a mailbox provider, a university, a list server, or a forwarding service, not to anything you send from.
  • SPF fails or passes for a domain that isn't yours.
  • DKIM either passes for your domain (DMARC passes) or fails (the message was modified).
  • Sometimes the receiver adds an override reason, such as trusted_forwarder (the failure was expected because the message came through a known and trusted forwarder), mailing_list, or local_policy.

In headers at the final recipient:

Authentication-Results: mx.recipient.example;
  spf=fail smtp.mailfrom=example.com;
  dkim=pass header.d=example.com;
  dmarc=pass header.from=example.com

That's a forward that survived: SPF failed on the forwarder's IP, but aligned DKIM carried DMARC. If you see dkim=fail (body hash did not verify) instead, something changed the body on the way.

Don't mistake these rows for spoofing. They're your own mail arriving by an indirect route. Classifying report rows is covered in Legitimate mail vs spoofing in reports and Reports show sources we do not recognize.

Why SPF fails on forwarded mail

SPF checks the IP address that hands the message over against the envelope sender's SPF record. After a forward, that IP is the forwarder's. Microsoft puts it simply: The forwarding server's IP isn't in the original sender's SPF record. This behavior is expected. The same: Even if SPF is correctly set up for your domain, forwarded messages can still fail SPF.

A typical case is an alumni address or a role address that relays to a real mailbox. Mail relayed that way will most likely fail SPF checks unless the envelope sender is rewritten by the relaying server. There's nothing to fix in your SPF record. Adding forwarders to it doesn't work, because you can't list every forwarder on the internet, and you'd authorize servers you don't control. Our main-site article on alignment issues covers the same point from the SPF side.

When DKIM breaks too

Plain forwarding usually leaves DKIM alone. DKIM signatures will generally remain valid in these relay situations. The signature breaks when someone changes what you signed:

  • A mailing list tags the Subject or adds a footer.
  • A security gateway or disclaimer tool rewrites the body after your signature was applied.
  • A forwarder re-encodes the message or changes signed headers.

Google warns that "forwarded messages can fail DKIM" even when DKIM is correctly set up, and Gmail "doesn't automatically authenticate forwarded messages that previously passed authentication". The DKIM mechanics, including what lists do to signatures and why l= isn't a fix, are in DKIM and mailing lists or forwarders. Reading DKIM failure reasons is in Why DKIM signatures fail.

Who can fix what

Who What helps
You, the original sender Sign every stream with DKIM aligned to your From domain (Identifier alignment for SPF and DKIM). That's what carries plain forwards through DMARC. Don't add forwarders to SPF.
The forwarder or list operator Avoid changing signed content. Rewrite the envelope sender (SRS or similar) so SPF and bounces work for the forwarder. Add ARC seals if supported. Yahoo tells forwarders: "If you forward emails, implement ARC."
The receiver May choose to trust ARC from intermediaries it knows. In Microsoft 365 that's the trusted ARC sealers setting. A Microsoft 365 tenant behind a third-party gateway can also use Enhanced Filtering for Connectors.

Notice what isn't in your column: you can't make a third party's forwarder stop editing mail, and you can't make a receiver trust ARC.

Where SRS and ARC fit

SRS helps SPF, not your DMARC. Microsoft is explicit: "SRS rewriting doesn't resolve the issue of forwarded messages not passing DMARC checks." After rewriting, SPF may pass for the forwarder's domain, but that domain doesn't align with your From. Microsoft's conclusion is that the only reliable way for DMARC to pass is a message "DKIM-signed using the domain in the From address" with the signature intact to the final destination.

ARC is a receiver's choice. The specification is experimental. An intermediary seals the authentication results it saw, and a later receiver may use them. In Microsoft 365, the trusted ARC sealers setting overrides DMARC authentication failures only, not spam filtering, and Microsoft 365 already trusts ARC seals from major providers such as Google and Yahoo. Google doesn't document equivalent ARC trust in the same way. None of the list-friendly methods, ARC included, have become widely used. Which receivers trust which sealers isn't consistently documented. Treat ARC as a help at some receivers, not a fix you can count on. SRS and ARC are covered in depth in Email forwarding, SRS, and ARC.

Forwarding and p=reject

This is where forwarding matters most. p=reject can be incompatible with indirect message flows such as alumni forwarders, role-based email aliases, and mailing lists, and domains publishing p=reject must apply valid DKIM signatures. Domains whose users post to mailing lists should not publish p=reject.

That isn't a reason to stay at p=none forever. It's a reason to make sure every stream is DKIM-signed and aligned, to check your reports for forwarder and list traffic, and to treat p=reject as a careful decision for each domain. The readiness checks are in When you are ready for p=reject.

Mistakes worth avoiding

  • Relying on SPF alone for DMARC. Forwarding is the first thing that breaks it.
  • Adding forwarder IPs or includes to your SPF record.
  • Reading forwarder rows as spoofing and blocking your own mail at enforcement.
  • Letting a gateway or disclaimer tool modify mail after it's signed. Sign after the last system that changes the message, or have that system re-sign.
  • Treating a forwarding service as a sending platform. A domain-wide forward relays mail; it doesn't make that mail authenticate as yours.
  • Expecting ARC or SRS to rescue mail that has no surviving aligned DKIM signature.

Free DMARC account

Not sure which sender is failing?

Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.

  • Every sending source in one dashboard
  • SPF, DKIM and alignment results per sender
  • No XML files to read

Create a free DMARC accountTalk to an expert

FAQ

Why does my mail fail SPF when someone forwards it?

The forwarder's server isn't in your SPF record. Microsoft calls this expected behavior.

How do I make forwarded mail pass DMARC?

Sign it with DKIM aligned to your From domain. Plain forwarding usually leaves the signature intact.

Will ARC fix it?

Only at receivers that choose to trust the forwarder's ARC seal.

Should I add the forwarder to my SPF record?

No. You can't list every forwarder, and you'd be authorizing servers you don't control.