REmail Deliverability Glossary

Return Path (Bounce Address / Envelope From)

The SMTP envelope address where delivery failure notifications are sent. SPF checks the Return-Path domain — mismatches cause DMARC alignment failures.

The Return Path (also called the envelope sender, MAIL FROM, or bounce address) is the email address where delivery failure notifications (bounces) are sent. It is set in the SMTP envelope and is often different from the visible From address.

Return-Path in email headers:

Return-Path: <bounce@yoursendingdomain.com>

Why it matters for deliverability:

  • SPF authentication checks the Return-Path domain, not the visible From address
  • Your bounce processing system must monitor the Return-Path address to handle bounces
  • Mismatches between Return-Path domain and From domain can cause DMARC alignment failures

Shared vs. custom Return-Path: Many ESPs use their own domain as the Return-Path by default. Using a custom Return-Path on your own domain improves authentication alignment and is recommended for high-volume senders.

Frequently Asked Questions

What is the Return-Path header and how does it affect SPF?

The Return-Path (also called the envelope sender or MAIL FROM) is the email address the SMTP server uses to identify where to send bounce notifications. Critically, SPF authentication checks the domain in the Return-Path — not the visible From address in the email client. If your ESP uses its own domain in the Return-Path (common with shared sending infrastructure), SPF aligns to the ESP's domain, not yours. This creates a DMARC alignment issue unless your DKIM signature aligns to your From domain. Always verify whether your ESP uses a custom Return-Path or their own domain.

How do I set up a custom Return-Path for better DMARC alignment?

Setting up a custom Return-Path involves configuring your ESP to use a subdomain of your sending domain as the envelope sender — for example, bounces.yourdomain.com. This requires adding a CNAME record in your DNS pointing your bounce subdomain to your ESP's bounce handling infrastructure, and enabling custom Return-Path in your ESP account settings. With a custom Return-Path on your own domain, SPF alignment passes for your domain, which strengthens DMARC alignment and keeps all authentication signals pointing to your domain rather than your ESP's infrastructure.

What happens to emails that bounce? Where does the bounce go?

Bounce notifications are delivered to the address specified in the Return-Path header. If your ESP controls the Return-Path (their domain), bounces go to their system and they handle bounce management. If you've configured a custom Return-Path, bounces arrive at that address and your systems must process them. Regardless of who receives the bounce notification, the key action is the same: hard-bounced addresses must be added to your permanent suppression list immediately. If your ESP handles bounces, verify they're automatically suppressing hard-bounced addresses and that you can export that list if you ever switch ESPs.

Related Terms

Get Started Today

Stop Guessing. Start Landing in the Inbox.

Improve your email deliverability with real engagement signals and full visibility into where your emails actually land.

Free 10-day trial · No credit card · Cancel anytime