Every email has two sender addresses: the Envelope From, which mail servers use to deliver the email and return bounce messages, and the Message From, which the recipient sees. This article is for anyone who wants to understand why these two addresses are sometimes different, for example when fixing an Invalid From Address error. After reading it, you'll know what each address does, when it's normal for them to differ, and how to check both on an email.
In this article, you'll learn how to:
- Tell the two sender addresses apart, using a posted letter as an example
- Recognise when it's normal for the two addresses to be different
- Understand how email providers check each address
- Check both addresses on an email you received
Envelope From and Message From explained
The easiest way to understand the two addresses is to think of a posted letter.
In a posted letter
A letter can name its sender in two places:
- The return address on the envelope. The post office returns the letter here if it can't be delivered.
- The sender's name and address inside the letter. This is what the person reading the letter sees.
These usually match, but they don't have to. For example, Ben Charles in California could post a letter written by Tony Rock in New York. The envelope shows Ben's address, and the letter inside is signed by Tony.
In an email
Email works the same way:
- Envelope From is the address mail servers use to deliver your email. If the email can't be delivered, the bounce message goes to this address. Recipients don't normally see it.
- Message From is the address in the From field. It's the sender the recipient sees in their inbox.
| Envelope From | Message From | |
|---|---|---|
| Postal equivalent | Return address on the envelope | Sender named inside the letter |
| Who uses it | Mail servers | The person reading the email |
| Shown in the inbox | No, only in the email's headers | Yes, in the From field |
| Bounce messages go to | This address | Not used for bounces |
| Also called | Return-Path, bounce address, Mail From, SMTP envelope sender | Header From |
| Example | ben.charles@xyzinc.com | tony.rock@zxinc.com |
What this looks like behind the scenes
When an email is sent, the sending server gives the Envelope From to the receiving server first, using a command called MAIL FROM. The Message From is part of the email itself. Here's a simplified example:
MAIL FROM:<ben.charles@xyzinc.com> ← Envelope From
RCPT TO:<recipient@example.com>
DATA
From: Tony Rock <tony.rock@zxinc.com> ← Message From
Subject: Quarterly report
The recipient sees only tony.rock@zxinc.com. If the email bounces, the bounce message goes to ben.charles@xyzinc.com.
When the two addresses are different
It's common for the Envelope From and Message From to be different. These are the usual reasons:
- Mailing lists. The list uses its own address as the Envelope From, so bounces go to the list. The Message From shows the person who wrote the post.
- Forwarding services. A service that forwards your email may set its own address as the Envelope From.
- Automated emails. Order confirmations and alerts often use a separate bounce address as the Envelope From and a no-reply address as the Message From.
- Third-party sending services. CRMs and email marketing tools send on your behalf. They use their own address as the Envelope From and your address as the Message From.
- Email aliases. When you send from an alias, the alias is the Message From, while your main mailbox can be the Envelope From.
- Spoofing and phishing. Scammers can set a Message From that looks like someone you trust. The Envelope From often shows their real domain.
|
✓ Tip A different Envelope From isn't a problem on its own. Take a closer look only when the email is unexpected or asks for personal details, passwords or payment. |
How email providers check these addresses
Email providers run security checks on both addresses to decide whether an email is genuine:
- SPF (a DNS setting that lists which servers can send email for a domain) checks the domain of the Envelope From.
- DKIM (a digital signature added to each email) checks that the email wasn't changed on the way and comes from the signing domain.
- DMARC (a policy that tells providers what to do with emails that fail these checks) checks that the Message From domain matches a domain that passed SPF or DKIM.
Because the Message From is what people see, DMARC makes sure it can't easily be faked. This is why you set up DKIM and DMARC for your domain.
Titan also checks the Message From when you send an email. If it doesn't match the account you're sending from, Titan rejects the email with an Invalid From Address error.
Check both addresses on an email
You can see both addresses in an email's full headers. Headers are the technical details behind every email, such as who sent it and the servers it passed through.
- Open the full headers of the email. For steps in Titan webmail, see Email Headers.
- In the headers, find the Return-Path line. The address on this line is the Envelope From.
- Find the From line. The address on this line is the Message From.
Example: Return-Path: <ben.charles@xyzinc.com> and From: Tony Rock <tony.rock@zxinc.com>
- Compare the domains of the two addresses (the part after the @).
You can now see both sender addresses and whether they come from the same domain.
Confirmation — what success looks like
You can now tell the two sender addresses apart: the Envelope From, shown in the Return-Path header, is where bounce messages go, and the Message From, shown in the From field, is what recipients see. When the two are different, you can check for a normal reason, such as a mailing list or sending service, before treating the email as suspicious.
Troubleshooting
Problem: Your email is rejected with an Invalid From Address error.
Cause: The Message From in your email app doesn't match the Envelope From (Mail From) of the account you're sending from.
Fix: Follow the steps in Fix an Invalid From Address error to make the two addresses match.
Problem: An email shows a sender you trust, but its Envelope From is an unfamiliar domain.
Cause: The sender may use a third-party sending service, or the email may be spoofed.
Fix: If you weren't expecting the email, don't click its links or open attachments. Contact the sender another way to check, and if you use Titan Mail, report the email with Report Phishing.