What the return-path domain does

When an email is sent, it can have more than one sender address. The From address is the one people usually see in their mail app. The envelope sender, also called the MAIL FROM address, is used during delivery to direct failure notices, or bounces. After delivery, the receiving system typically records that envelope sender in a Return-Path header.

An email service may use its own domain for the envelope sender by default. A custom return-path domain lets it use a domain you control instead, such as bounces.example.com. The service still needs a way to receive and process bounces sent to addresses at that domain. You should not need to create a mailbox for each address the service generates.

This setup is useful when you want SPF checks to use a domain associated with your organization, rather than only the provider’s domain. It does not change the visible From address, guarantee inbox placement, or replace DKIM and DMARC.

Choose a dedicated subdomain

A dedicated subdomain keeps bounce-related DNS separate from records used by your website and ordinary mailboxes. For example, if your visible From address is news@example.com, you might choose bounces.example.com as the custom return-path domain. Use an exact name supported by your email service; providers may call this feature a custom MAIL FROM domain, bounce domain, or return-path domain.

Check whether the subdomain is already in use before changing its records. In particular, avoid replacing an MX record that delivers regular mail or a CNAME used by another service. You will usually make the DNS changes wherever the domain’s authoritative DNS is managed, which may be different from the company where the domain was registered.

Add the records your provider requires

Start in your email service’s domain settings and enter the chosen return-path subdomain. The service should show the DNS records it expects. Depending on the provider, these may include an MX record directing bounces to its systems, a TXT record authorizing its senders for SPF, or a CNAME that delegates part of the configuration to the provider. Copy the specified record names and values exactly; do not guess an MX destination or SPF include value.

Pay attention to how your DNS dashboard handles record names. Some dashboards automatically append your domain, so entering the full hostname could accidentally create a name such as bounces.example.com.example.com. Before saving, check the final hostname shown for each record.

If the provider calls for an SPF TXT record at bounces.example.com, check whether one already exists at that exact name. A hostname should have one SPF policy, not multiple competing SPF records. If you need to authorize more than one sender there, combine the permitted mechanisms into a single policy according to the services’ instructions. A CNAME also cannot share its hostname with other record types, so follow the provider’s requested record pattern rather than mixing patterns from different guides.

Understand SPF and DMARC alignment

SPF checks whether the sending server is authorized by the domain used for the envelope sender. With a custom return-path domain, SPF may pass for bounces.example.com if its DNS policy authorizes the email service. SPF passing alone, however, does not mean the message passes DMARC.

DMARC compares the domain in the visible From address with the domain authenticated by SPF or DKIM. Under relaxed SPF alignment, bounces.example.com can align with a From address at example.com because they share the same organizational domain. Under strict SPF alignment, those domains are not an exact match. If your DMARC configuration requires strict alignment, check the provider’s options before relying on the custom return-path domain for SPF alignment. An aligned DKIM signature is another way for a message to satisfy DMARC.

Verify delivery and bounce handling

After adding the DNS records, return to the email service and use its verification check if one is available. DNS changes may take time to become visible, so a failed check immediately after saving does not necessarily mean the records are wrong. If verification continues to fail, compare the published hostname, record type, and value against the provider’s instructions.

Send a test message to an address you control and inspect its full headers. Look for the Return-Path domain and authentication results for SPF, DKIM, and DMARC. The return-path address may contain a provider-generated identifier; the important point is whether its domain is the one you configured. Then use the provider’s supported test method to confirm that bounces appear in its reporting or event system. Avoid testing with an unrelated person’s address or sharing full message headers publicly, since headers can contain addresses and other identifying details.

Back to category ↗