Return-Path header
The Return-Path is the envelope sender address where bounces go. How it differs from From and Reply-To, why SPF checks it, and how Sendly sets it.
The Return-Path is the email address a message's delivery failures are sent back to. It is
also called the envelope sender, the bounce address, the SMTP MAIL FROM address or the
5321.MailFrom. It is not the address a reader sees: that is the From header. Every
message carries both, and they are allowed to be different domains.
They are separate on purpose. A mailing list can relay your message to a thousand people and take the bounces itself, without rewriting the From address the reader sees.
What is the difference between Return-Path, From and Reply-To?
Three addresses can appear on one message, and each is used by something different.
| Property | Return-Path | From | Reply-To |
|---|---|---|---|
| Also called | Envelope sender, bounce address, MAIL FROM | Header From, 5322.From | Reply address |
| Where it lives | The SMTP envelope; copied into a header on delivery | A message header you write | A message header you write (optional) |
| Shown to the reader | No, only in the raw source | Yes, as the sender | Only when they reply |
| Used for | Bounces and delivery failure notices; the identity SPF checks | Who the message claims to be from; the identity DMARC protects | Where a reply is addressed, instead of From |
| Set by | The sending server | You | You |
In short: the Return-Path decides where bounces go, From decides who the message claims to be from, and Reply-To decides where replies go.
Where does the Return-Path come from?
The Return-Path is not a header the sender writes. During the SMTP conversation the
sending server announces the envelope sender with the MAIL FROM command, which is why
it is also called the SMTP Return-Path or MAIL FROM address. The server that
finally delivers the message records that address at the top of the message as a
Return-Path: header (RFC 5321, section 4.4). Writing a Return-Path header into the
message yourself does not change the envelope; the delivering server writes the one that
counts.
Messages that report a failure, such as a bounce notice, are sent with an empty envelope
sender (<>), so that a failure about a failure can never loop.
How do I see the Return-Path of a message?
Open the raw source of a message you received. The two addresses sit side by side and can be completely different:
Return-Path: <0100019a...-000000@sendly.yourdomain.com>
From: Acme <hello@yourdomain.com>
To: customer@example.com
Subject: Your receipt- Gmail: open the message, choose the three-dot menu, then Show original. The
Return-Path:line is near the top of the raw message. - Outlook: open the message and view its internet headers (View message source or
View message details in Outlook on the web, File > Properties in the desktop app),
then look for
Return-Path:.
Why does SPF check the Return-Path and not the From address?
SPF was designed to protect the SMTP envelope. A receiving server asks:
is the server that is handing me this message allowed to send for the MAIL FROM domain?
It does not look at the From header at all (RFC 7208). So a message can pass SPF on a domain
the recipient never sees, and a message that shows your domain in From can still pass SPF
on the sender's own envelope domain. That gap is exactly what DMARC was built to close.
How does the Return-Path affect DMARC alignment?
DMARC passes a message when SPF or DKIM passes and aligns with the From domain. For SPF, alignment means the Return-Path domain matches the From domain:
- Relaxed alignment (the default): the Return-Path domain only has to share the same
organizational domain, so
sendly.yourdomain.comaligns withhello@yourdomain.com. - Strict alignment: the two domains must be identical.
If your provider uses its own domain as the Return-Path, SPF can pass and still not align, and DMARC then depends entirely on DKIM. A Return-Path on your own domain is what makes SPF count towards DMARC.
What is a custom MAIL FROM domain?
A custom MAIL FROM domain is a subdomain of your sending domain that you point at your provider, so the Return-Path is an address on your domain instead of the provider's. It takes two DNS records on that subdomain: an MX record, so bounces and complaints are routed back to the provider, and a TXT record carrying an SPF policy that authorizes the provider to send for it. The subdomain is separate from your From domain, so it does not change where your own mail is received.
What happens to bounces sent to the Return-Path?
Bounces arrive at the Return-Path. If that address is not monitored by whatever sends your mail, nobody learns that an address is dead, and you keep mailing it, which is a direct hit to sender reputation. A sender that reads its bounces can stop mailing the dead address and add it to a suppression list.
In Sendly
Sendly sends through Amazon SES and gives every sending identity a custom MAIL FROM
subdomain: sendly.yourdomain.com for yourdomain.com. Once its MX and SPF records are
published (see Custom MAIL FROM),
the Return-Path on your mail is an address on that subdomain, unique to each message, as in
the example above. That gives you two things:
- SPF alignment. The envelope domain is a subdomain of your From domain, which is what DMARC's relaxed SPF alignment requires.
- Bounce handling. Bounce and complaint reports come back through SES and are processed for you, and the affected addresses land on your suppression list automatically.
You never choose or monitor the address itself. If the MX record on the subdomain is
missing, mail still sends, but SES falls back to its own amazonses.com envelope sender,
and SPF no longer aligns with your domain. The domain's
MAIL FROM status in Sendly tells you which case you are in.
To publish the records, follow Verifying sending domains or let guided DNS setup do it. Related terms: sending domain and MX record.