Sales Loves MarketingThe return path is the address that receives bounce messages when an email can't be delivered. It is set in the SMTP "MAIL FROM" command, saved as a Return-Path: header when the message arrives, and it is usually hidden from the reader. You may also see it called the envelope sender, bounce address or reverse path.
How does the return path work?
Every email has two sender addresses:
- The From address (
RFC5322.From) is what the recipient sees in their inbox. - The return path (
RFC5321.MailFrom) is what mail servers use behind the scenes.
When your server sends a message, it gives the return path in the MAIL FROM command. If a server later can't deliver the message, RFC 5321 says it must send a failure notice to the originator "as indicated by the reverse-path." That is the bounce you receive.
When the message reaches its destination, the server that makes final delivery adds a Return-Path: line to the top of the message. RFC 5321 says this line "preserves the information in the from the MAIL command."
Why does the return path matter for email marketing?
Bounce handling. Bounces go to the return path, not to your From address. Email platforms use their own return path so they can process bounces and stop sending to dead addresses, which protects your deliverability.
SPF and DMARC. SPF checks whether the sending server is allowed to send for the return path's domain. DMARC, now defined in RFC 9989, says it "relies solely on SPF validation of the MAIL FROM identity." For SPF to count towards DMARC, that domain must align with your From domain. In relaxed mode, the default, bounces.example.com aligns with example.com. In strict mode, the two must match exactly.
Google's requirements. Google's sender guidelines require bulk senders to Gmail to have the From domain aligned with either the SPF domain or the DKIM domain. A custom return path is one way to get SPF alignment.
How do you set up a custom return path?
The exact steps depend on your email platform, but the pattern is the same:
- Pick a subdomain of your sending domain, for example
bounces.example.com. See subdomain. - Add a CNAME record in your DNS that points that subdomain to the host your email platform gives you.
- Verify it in the email platform. The platform checks the record and starts using the subdomain in MAIL FROM.
- Test. Send a message to yourself and check the headers. The
Return-Path:should show your subdomain, and the SPF result should pass.
Example
A SaaS company sends its newsletter from news@example.com through an email platform. Without a custom return path, the return path sits on the platform's own domain, so SPF passes for the platform's domain but does not align with example.com. After the team adds a CNAME for bounces.example.com, SPF passes on a domain that aligns with the From address, and DMARC can pass on SPF as well as DKIM.
Frequently asked questions
Is the return path the same as the From address?
No. The From address is what recipients see. The return path, also called the envelope sender, bounce address or MAIL FROM, is used by servers to send back failure notices. They can be different addresses, and often are when you send through an email platform.
What is a custom return path?
It means your email platform uses an address on your own subdomain, such as bounces.example.com, as the return path instead of its own domain. This lets SPF pass on a domain that aligns with your From address, which helps DMARC.
Who sets the Return-Path header?
The receiving server that makes final delivery adds it. RFC 5321 says it inserts a return-path line at the start of the message that preserves the address from the MAIL FROM command. Senders should not add their own Return-Path header.