Skip to content
AdminKit

Envelope sender vs header From

What is Envelope sender vs header From?

An email carries two separate addresses: the envelope sender, used only for routing and bounces (RFC 5321), and the header From address a mail client actually displays (RFC 5322). SPF checks only the envelope sender, which is why a message can pass SPF while showing a forged header From. AdminKit's backscatter guide explains why this gap matters.

By AdminKit team, Netbase JSC · Updated

An email has two different “sender” addresses that are often confused. The envelope sender is the address given in the SMTP MAIL FROM command (RFC 5321, whose IETF Datatracker entry lists the errata and updates filed against it), used only for routing and bounce delivery between mail servers; the header From address is the human-readable “From:” field (RFC 5322) a mail client actually displays to the recipient. The final delivering server records the envelope sender in a Return-Path header at the top of the delivered message. Nothing requires the two to match, and legitimate setups — mailing lists, some forwarding services — routinely set them differently; M3AAWG’s Sending Domains Best Common Practices itself recommends putting the Return-Path (envelope sender) on a different subdomain than the visible From address as deliverability best practice, not a misconfiguration. SPF checks the envelope sender’s domain against the connecting server’s IP, not the header From a reader sees, which is why a message can pass SPF while still displaying a different, even forged, header From address. Microsoft’s DMARC setup guide uses other names for the same pair — the 5321.MailFrom address (also called the P1 or envelope sender) and the 5322.From address (the P2 sender) — and notes that SPF and DKIM on their own don’t require those two domains to align; DMARC is what adds that check. Spammers exploit the gap by forging an uninvolved third party’s address as the envelope sender, so any bounce generated for an undeliverable message lands on that victim instead of the real sender — the mechanism behind email backscatter. The same gap explains why WooCommerce emails go to spam when the web server uses its own envelope sender behind a store-domain From address.

AdminKit groups envelope sender vs header From under its email authentication cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

Why can an email pass SPF but still show a forged header From?

Because SPF checks only the envelope sender's domain against the connecting server's IP, not the header From address a reader actually sees.

What is the envelope sender used for?

Routing and bounce delivery between mail servers -- it's the address given in the SMTP MAIL FROM command, not something a mail client normally displays.

Do the envelope sender and header From have to match?

No -- nothing in SMTP requires it, and legitimate setups like mailing lists and some forwarding services routinely set them differently.