Return-Path
The Return-Path is the email header that records where bounce messages should be sent. The final delivery server writes it from the SMTP MAIL FROM value, as specified in RFC 5321. You cannot set it directly by adding a header; the receiving server strips that and uses the envelope sender. The domain in it is what SPF authenticates.
- It is the persistent record of the envelope sender, written into the header on delivery
-
You cannot set it by hand; the receiving server overwrites it with the
MAIL FROM - Its domain is the one SPF checks, so a custom Return-Path drives SPF alignment
-
Aligning it with your
Fromdomain helps your mail pass DMARC
Return-Path:
MAIL FROM
What the Return-Path is
The Return-Path is a header field that names the address where bounce messages and other delivery notifications should go. It is not something the sender types in. Per RFC 5321 section 4.4, when the final delivery server accepts a message it inserts a single Return-Path line at the top of the header, copied from the envelope sender (the MAIL FROM value used during the SMTP transaction).
In other words, the envelope sender and the Return-Path are the same address at two different moments: the envelope sender is the live value during transmission, and the Return-Path is that value preserved in the delivered message. This is also why any Return-Path header you try to add yourself is ignored; the receiving server strips it and writes its own from what actually arrived in MAIL FROM.
Return-Path: <bounce@mail.example.com>Return-Path, SPF, and alignment
The Return-Path domain is the one SPF authenticates, which makes it central to DMARC. DMARC does not just want SPF to pass; it wants the passing domain to align with the visible From domain. When you send through an ESP, the default Return-Path is usually on the ESP’s own domain, so SPF passes but does not align with your From, and DMARC can still fail on the SPF side.
The fix is a custom Return-Path, often a subdomain like mail.example.com that you point at your ESP with the DNS records they provide. Now the Return-Path is on your own organizational domain, SPF passes and aligns, and DMARC is satisfied. Most ESPs document this under “custom Return-Path,” “custom MAIL FROM,” or “domain authentication.” You can confirm the result with our SPF checker.
Return-Path vs From header
Common mistakes
Return-Path header in your message has no effect; the receiving server discards it and writes its own from the SMTP MAIL FROM. Control it through the envelope sender, not the header.Reply-To sets where human replies go and is part of the visible message. They solve different problems.