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

Envelope From vs Header From

The Envelope From is the sender address servers use while a message is in transit. It's where bounces go, and it's the address SPF checks. The Header From is the address people see in their mail client. DMARC cares about the Header From: it passes only when SPF or DKIM passed for a domain that's aligned with it. The two addresses are often different, usually for good reasons, and that's exactly why SPF can pass for a vendor's domain while DMARC still fails for yours.

The two "From" addresses

An email has two layers. The envelope is what servers exchange during the SMTP conversation. The message is the headers and body your recipient reads. Each layer has its own sender.

Envelope From Header From
Formal name MAIL FROM (the reverse-path in the SMTP MAIL FROM command) Header From (the From: header field)
Other names Return-Path, bounce address, MAIL FROM, envelope sender, P1 sender From address, author address, P2 sender; in DMARC, its domain is the "Author Domain"
What it's for Reporting delivery errors (bounces) Telling the reader who wrote the message
Who sees it Servers; mail clients don't normally show it Everyone; it's shown in the mail client
Which check uses it SPF DMARC

The reverse-path can be used to report errors, which is why people call it the bounce address. It can even be empty (MAIL FROM:<>), which is what bounce messages themselves use. In that case SPF checks postmaster@ the HELO domain instead.

The From: header is the mailbox of the person or system responsible for the writing of the message. DMARC only evaluates messages whose From header contains exactly one domain; anything else is outside its scope.

Which check looks at which identity

  • SPF checks the Envelope From domain (and can check the HELO name too). DMARC only uses the SPF result for the Envelope From, never the HELO result.
  • DKIM checks the signing domain in the d= tag of the DKIM-Signature header. That domain isn't required to match any visible address, though the From header must be one of the signed fields.
  • DMARC passes when SPF or DKIM passed and the passing domain is aligned with the Header From domain. One aligned pass is enough; at least one, preferably both, is the usual advice.

For the definitions of SPF itself, see What is SPF on our main site; for how the three checks fit together, see What is email authentication?.

How DMARC alignment uses the Header From

Precise wording matters here. DMARC doesn't "align the Header From." It checks whether the domain that SPF or DKIM authenticated is aligned with the Header From domain.

There are two modes:

  • Relaxed: the two domains share the same organizational domain. bounce.example.com aligns with news.example.com, because both sit under example.com.
  • Strict: the domains must be identical.

The aspf and adkim tags set the mode. Nearly all domain owners find relaxed alignment sufficient.

A worked example: SPF passes for the vendor, not for you

You send a newsletter through a marketing platform. The SMTP conversation and headers look like this:

MAIL FROM:<bounces@mail.vendor.example>

From: "Example Co" <news@example.com>
  • SPF checks mail.vendor.example. The platform's servers are listed there, so SPF passes.
  • The Header From domain is example.com. vendor.example isn't aligned with it.
  • If the platform also signs DKIM with d=vendor.example, DKIM passes but isn't aligned either.
  • No aligned pass, so DMARC fails.

Nothing in that mail is forged. The platform just hasn't been set up to send as you. This is one common reason legitimate mail lands in spam or bounces (Why are my emails going to spam). The fix is one or both of these:

  1. A custom bounce (MAIL FROM) domain under your domain, such as bounce.example.com, so SPF passes for something aligned with example.com.
  2. DKIM signing with d=example.com, usually by publishing the selector record or CNAMEs the platform gives you.

The same checklist applies for third-party senders under Outlook.com's high-volume rules (Google, Yahoo, and Microsoft sender requirements). If a platform shows a message like "SPF record not found for custom MAIL FROM domain," it's telling you it checked the bounce subdomain you configured and didn't find the SPF record it expects there; its setup page lists what to publish.

Note what doesn't fix it: adding the vendor's include: to your own SPF record. That helps when the vendor sends with your domain in the envelope. If the vendor still uses its own bounce domain, SPF passes for that domain and still isn't aligned.

How to read email headers to find both addresses

When a message is finally delivered, the receiving server adds a Return-Path: header that records the Envelope From. So in a delivered message, look for two lines:

Return-Path: <bounces@mail.vendor.example>
From: "Example Co" <news@example.com>

And the receiver's verdict, if it adds one:

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

smtp.mailfrom is the Envelope From domain SPF checked, header.d is the DKIM signing domain, and header.from is the Header From domain DMARC compared them against.

In Gmail, open the message and use Show original from the message menu to see the full headers.

Across thousands of messages, the same comparison shows up in your DMARC aggregate reports, source by source.

Not the same as the Header From

Three other things often get mistaken for it:

  • The display name ("Example Co") is free text. DMARC doesn't check it, and display-name attacks are outside its scope.
  • Reply-To is where replies are suggested to go. DMARC doesn't evaluate it. And it isn't the Return-Path: Return-Path is where bounces go, Reply-To is where human replies go.
  • Sender names the system that transmitted the message when it differs from the author. DMARC doesn't use it either.

Mistakes worth avoiding

  • Reading "SPF pass" in a report and assuming DMARC passed.
  • Leaving a platform on its default bounce domain and its default DKIM domain, so nothing aligns.
  • Assuming the Envelope From must always equal the Header From. With relaxed alignment, the same organizational domain is enough, and aligned DKIM on its own satisfies DMARC.
  • Assuming p=reject stops someone from putting your domain in the envelope or Reply-To. DMARC policy is keyed to the Header From domain.

Free DMARC account

Turn raw DMARC reports into a readable dashboard

Point your rua address to our platform and read the results by sender and source instead of opening XML files.

  • Results grouped by sending source
  • SPF, DKIM and alignment results per sender
  • The original XML reports are still there to download

Create a free DMARC accountTalk to an expert

FAQ

Is Return-Path the same as Reply-To?

No. Return-Path records the Envelope From, where bounces go. Reply-To is where people's replies go, and DMARC doesn't evaluate it at all.

Do I need a custom Return-Path?

Not if DKIM is aligned, because one aligned pass satisfies DMARC. Having both aligned is sturdier, and since forwarding usually breaks SPF, aligned DKIM is the more resilient of the two.

Does DMARC protect the display name?

No. It only evaluates the domain in the From header.