The Return-Path is the address where bounce notifications and other delivery feedback are sent. It is defined in the email header under the Return-Path field.
A typical Return-Path might look like this:
Return-Path: <pm_bounces@pm.mtasv.net>
You may also see it referred to as:
Bounce address
Envelope From / MAIL FROM
Reverse Path
Why use a custom Return-Path?
Using a custom Return-Path that matches your domain helps build and preserve your sending reputation. It also plays an important role in DMARC authentication.
For DMARC to pass, the domain used in the Return-Path must align with the domain in the From address (this is known as SPF alignment).
Example:
From Address | Return-Path | DMARC Alignment | Result |
|---|---|---|---|
info@example.com | pm_bounces@pm.mtasv.net | Not aligned | SPF fails for DMARC |
info@example.com | pm_bounces@pm-bounces.example.com | Aligned | DMARC passes |
With a custom Return-Path, the email header would look like:
Return-Path: <pm_bounces@pm-bounces.example.com>
This ensures that the sending identity is consistent and recognized as trustworthy.
How to set up a custom Return-Path
To use your domain for the Return-Path, create a CNAME DNS record that points to the sending service. For example:
pm-bounces.example.com CNAME pm.mtasv.net
This allows bounce reports and feedback to continue to be processed correctly by the mail provider.
