What is the Return-Path? (envelope from)

Definition

The Return-Path is the address given during the SMTP conversation itself, in the MAIL FROM command, before the message content is ever transmitted. It goes by several names that all mean the same thing: envelope from, envelope sender, bounce address, 5321.MailFrom (after RFC 5321, the SMTP standard). It has two jobs: it is where bounces and delivery failures are returned, and it is the address SPF is checked against.

Why it usually is not your address

When you send through an email service provider, the provider typically sets the Return-Path to an address on its own infrastructure, something like bounce-123@mailer.example-esp.com, so it can collect your bounces and manage your list hygiene automatically. Your readers never see it; the visible From: line still shows your domain. That split is normal and allowed, and it is exactly why DMARC alignment exists: an SPF pass on the provider's bounce domain says nothing about your domain unless the two match.

Where you can see it

Receivers stamp the envelope sender into a Return-Path: header at final delivery, so you can inspect it in any received message: open the raw source (in Gmail, “Show original”) and look at the top. If the domain there is not yours, your SPF pass belongs to your provider, and DKIM is what carries your DMARC result.

What it means for DMARC

• SPF authenticates the Return-Path domain, not the visible From. DMARC then requires the two to align for the pass to count.
• Many providers offer a custom Return-Path (a CNAME like bounce.yourdomain.com pointing at the provider) precisely to restore that alignment. If your provider offers one, turn it on.
• A forwarder relays from its own server, so SPF on the original Return-Path fails in transit (a forwarder that rewrites the Return-Path passes SPF for its own domain instead, which does not align). That is why forwarded mail needs DKIM to survive DMARC.