Blog/ Email glossary & concepts

Envelope Sender vs Header From: Email's Two From Addresses

Nafiul HasanNafiul Hasan· 11 min read
Diagram contrasting an email's envelope sender (the SMTP MAIL FROM, recorded as Return-Path) with the header From address the reader actually sees.

The short answer

The envelope sender is the address in the SMTP MAIL FROM command, saved as Return-Path. Mail servers use it for routing and bounces. The header From is the address your email app shows. They can differ: SPF checks the envelope sender, while DMARC ties the visible From back to an authenticated domain.

The envelope sender (MAIL FROM, Return-Path) handles delivery and bounces; the header From is what you see. How SPF and DMARC treat each.

On this page
  1. 01What is an envelope sender?
  2. 02Envelope sender and receiver: RCPT TO vs the To line
  3. 03The short version: two addresses, two jobs
  4. 04Envelope sender vs header From at a glance
  5. 05The envelope sender: MAIL FROM, Return-Path, and where bounces go
  6. 06How to see the envelope sender
  7. 07The header From: what you actually see
  8. 08Does SPF check the From address? No, and that is the point
  9. 09Why does Gmail show 'sent via another domain'?
  10. 10When the 'via' note matters, and when it does not
  11. 11Who needs to care about which
  12. 12What a mail client can do about the gap

The envelope sender is the address given in the SMTP MAIL FROM command. Mail servers use it for routing and for sending bounce messages, and it is saved in the Return-Path header. The header From is the address your email app shows. SPF checks the envelope sender; DMARC checks the header From.

They usually match. When they do not, the mismatch is either completely normal or a warning sign, and this article is about telling the two apart. The same split explains bounce handling and Gmail's 'via' notice.

In one line

The envelope sender is where bounces go. The header From is who the message says it is from.

What is an envelope sender?#

An envelope sender is the return address on the outside of an email. The sending server states it in the SMTP conversation with the MAIL FROM command, defined in RFC 5321, before any of the message itself is sent. You will also see it called the envelope from, the SMTP envelope sender, or the envelope sender address.

Think of a paper letter. The envelope carries the delivery details, and the letter inside carries a printed letterhead. The post office only reads the envelope, and it can say something different from the letterhead.

People also search for the MAIL FROM header, but MAIL FROM is not a header. It is an SMTP command, and the closest thing to it in a finished message is the Return-Path header.

Envelope sender and receiver: RCPT TO vs the To line#

The SMTP envelope has a receiving half too. After MAIL FROM, the sending server names each destination mailbox with an RCPT TO command. Those envelope recipients decide where the message is actually delivered.

The To and Cc lines you read are headers inside the message, and servers do not route on them. That is why a blind copy works: the Bcc recipient gets an RCPT TO, and the Bcc line is normally removed before delivery, so that person usually exists only in the envelope.

The short version: two addresses, two jobs#

The envelope sender's job is delivery: routing the message and receiving a bounce if delivery fails. The header From is the From: line defined in RFC 5322. Its job is human: it tells the reader who wrote the message.

Because they serve different jobs, they are allowed to hold different addresses. A newsletter often has the brand in the header From and the sending platform in the envelope sender. That is legitimate. The trouble starts only when you assume the visible From has been checked, because on its own it has not.

Envelope sender vs header From at a glance#

Here is the whole distinction in one view. Most email-authentication confusion comes from mixing up which column a rule applies to, so keep this table handy.

Envelope senderHeader From
Also calledEnvelope from, 5321.MailFrom, Return-Path, bounce address5322.From, display From, the author
Defined byThe SMTP MAIL FROM command (RFC 5321)The From: header (RFC 5322)
Part ofThe SMTP envelope, the delivery conversationThe message content, what is inside the email
Who sees itMail servers; hidden from the reader by defaultThe reader, in every mail app
What it is forRouting, and where bounces are returnedTelling the reader who wrote the message
Recorded asThe Return-Path: header the receiving server addsThe From: header the sender writes
Authenticated bySPF (and the separate HELO check)DMARC alignment, not SPF
Can be forged?Set by the sending server; checked by SPFJust text: anyone can type any name and address
Appears in Gmail asNot shown directly; a 'via' domain appears when the sending domain differs from the From domainThe name and address at the top of the message

The envelope sender: MAIL FROM, Return-Path, and where bounces go#

RFC 5321 calls the address in the MAIL FROM command the reverse-path, and says it 'contains the source mailbox... which can be used to report errors.' In plain terms, this is the address that receives bounces.

You do not normally see the envelope sender, but it leaves a trace. When the delivery server makes final delivery, RFC 5321 says it inserts a Return-Path: line at the top of the message, preserving the reverse-path from the MAIL command. So the Return-Path header in an email's raw source is the envelope sender, written down.

It also answers the bounce question directly. If a message cannot be delivered, the error report goes to the envelope sender, not to the From address the reader sees. Email platforms rely on this: they set a Return-Path on their own domain so bounces land in their system, while your brand stays in the From line.

A single email splitting into two paths: the envelope sender (MAIL FROM) flowing to the mail servers and the returned-bounce destination, and the header From flowing to the reader's inbox display.
The envelope sender routes the message and catches bounces; the header From is only ever shown to the reader.

Five names, one address

Envelope sender, envelope from, 5321.MailFrom, Return-Path, and bounce address are all the same address, seen from different stages of delivery. When a tool uses one of these terms, translate it to 'the address bounces go to' and the meaning rarely changes.

How to see the envelope sender#

Your mail app hides it, but the receiving server has already written it into the headers. Open the headers and look for the Return-Path line. These paths come from each vendor's help pages as of November 2026, and labels can differ by version.

  1. 1

    Gmail on the web

    Open the message, click More next to Reply, then choose Show original.

  2. 2

    Apple Mail on Mac

    Open the message, then choose View > Message > All Headers.

  3. 3

    New Outlook and Outlook on the web

    Open the message, select More actions at the top, then View > View message details.

  4. 4

    Classic Outlook for Windows

    Double-click the message to open it in its own window, then choose File > Properties and read the Internet headers box.

What the raw headers look like
Return-Path:<[email protected]>
Authentication-Results:mx.example.net; spf=pass smtp.mailfrom=mail.brand-esp.com; dkim=pass header.d=brand.com; dmarc=pass header.from=brand.com
From:Brand News <[email protected]>

The header From: what you actually see#

The header From is the From: field defined in RFC 5322, section 3.6.2. The standard says it 'specifies the author(s) of the message, that is, the mailbox(es) of the person(s)... responsible for the writing of the message.' It is the address every mail client displays at the top of the email.

It is content: the sender writes it, the same way they write the subject line. Nothing in the SMTP delivery layer forces it to match the envelope sender. RFC 5322 also defines a separate Sender: header for when the person who sent the message is not its author, with a secretary as the standard's own example.

So a message sent from an attacker's own server can still display a From line reading PayPal, service at paypal.com. This is display-From spoofing, and it is why the From address alone is not proof of who sent an email.

A From address is a claim, not proof

The From line is unauthenticated text on its own. Passing SPF does not make the visible From genuine, because SPF never looked at it. Treat a familiar name in the From field as a claim to verify, especially on anything asking for money, credentials, or urgent action.

Does SPF check the From address? No, and that is the point#

No, and this is the most useful thing to understand in the whole topic. As what is SPF explains, SPF, defined in RFC 7208, authenticates the envelope sender (the RFC5321.MailFrom identity) and the server's HELO name. It does not check the From: header the reader sees.

RFC 7208 warns that checking other identities against an SPF record 'is NOT RECOMMENDED,' partly because almost all mailing lists rewrite the MAIL FROM identity while some leave other identities unchanged.

The consequence is the gap that catches people out: a message can pass SPF and still carry a forged From line. An SPF pass means the sending server was authorized for the envelope sender's domain, and nothing more.

DMARC closes the gap. DMARC, defined in RFC 9989 (published May 2026, replacing RFC 7489), requires the header From domain to align with a domain that actually authenticated: either the SPF-checked envelope domain, or the domain that signed the message with DKIM. See DMARC alignment for how that match works. In the raw example above, SPF passed for the platform's domain, and DMARC still passed because DKIM signed as brand.com.

Why does Gmail show 'sent via another domain'?#

Once you can see the two addresses, the 'via' note stops being mysterious. Google says Gmail adds it when the domain the message was sent from does not match the domain in the From address.

The everyday example is a newsletter. The From line says a brand address, but the message was sent through an email platform on a different domain, and the brand has not set up authentication for it. Google also lists one narrower case: mail sent to a Google Group from a domain with a strict DMARC policy.

One message, two addresses
MAIL FROM (envelope)[email protected]
Return-Path (added on delivery)[email protected]
From (what you see)Brand News <[email protected]>
Gmail shows[email protected] via mail.brand-esp.com

When the 'via' note matters, and when it does not#

That note is usually not a problem. It is the normal shape of mail sent through a third-party platform, and a visible symptom of the same split: what you see is not always what authenticated.

Senders remove it by authenticating with the From domain: an SPF record that includes the platform, and a DKIM signature tied to their own domain. That alignment is also what lets DMARC pass, so fixing one fixes the other. Recipients cannot remove it. The exact wording is Gmail's presentation and can change, but the mechanism is stable across providers.

Who needs to care about which#

Which address you should focus on depends on what you are trying to do.

  • Reading email: the header From is what you judge a message by, but never on its own. A name you recognise plus an unexpected request is exactly the pattern spoofing exploits.
  • Running a mail server or app: the envelope sender is what you set for bounces and what SPF authenticates. Get the Return-Path right or your bounce handling breaks quietly.
  • Sending marketing or transactional mail: align the envelope sender and DKIM domain with your From domain. That is what removes the 'via' note and lets DMARC pass.
  • Securing an organisation: assume the From line is spoofable and lean on DMARC alignment, not SPF alone, to decide whether a message's visible sender can be trusted.

What a mail client can do about the gap#

No mail client can change how SMTP works. The two addresses are part of the protocol, and any tool claiming to fix the split is misdescribing it. What a client can do is read the authentication results already in the headers, so you do not have to open the raw source.

AI Emaily's spam and phishing scoring does that at sync. It reads the SPF, DKIM and DMARC results in each message's headers and uses a failed result, or a Return-Path domain that differs from the From domain, as signals in the score, alongside others such as brand impersonation and deceptive links. A mismatch alone counts for little, since newsletters do it all the time. We build AI Emaily.

The honest limit: it relies on the receiving provider's DMARC result rather than running its own alignment check, and it is a mail client, not a DMARC monitoring service. It does not publish or audit your domain's DNS records, and it will not generate aggregate DMARC reports for a domain you send from. That is a separate class of tool.

Frequently asked

Nafiul Hasan

Written by

Nafiul Hasan

Nafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.

EntrepreneurAI Automation System BuilderAI EnthusiastBuilds AI Enterprise Solutions10+ years experience
More from Nafiul
Ready when you are

Stop trusting the From line by itself

AI Emaily reads the SPF, DKIM and DMARC results in your mail and uses them, with other signals, in its spam and phishing scoring.

  • 7-day free trial
  • Cancel anytime
  • Every provider