Setting up a custom return path offers several practical benefits for authentication, deliverability, and brand consistency.
When your Return Path domain matches your From domain, your messages can properly align for DMARC. This is especially important if your domain uses a quarantine or reject DMARC policy. Without alignment, messages may fail DMARC even if SPF technically passes.
Mailbox providers place more trust in mail authenticated with your own domain rather than a shared sending domain. Using a custom return path helps reinforce that trust and can support stronger inbox placement over time.
Outlook and some other inbox providers may display a “sent on behalf of” message when SPF is not aligned with your From domain. A custom return path resolves this by bringing your authentication into alignment.
With a custom return path, your sending reputation is tied directly to your domain. This gives you more control and clearer visibility into how your mail is performing, rather than sharing reputation signals across multiple senders.
Even though the bounce domain changes, Delivra continues to process and manage bounce messages as usual. No additional workflow changes are required on your end.
Before moving forward, there are a couple of site level details to review.
Once enabled, the custom return path applies to all accounts within the site. It cannot be configured differently per account.
Because the return path is shared across the site, all accounts should send from the same root domain. For example, if you configure bounces.example.com, all sending domains should align with example.com.
If you manage multiple brands or domains within a single site, confirm that this structure fits your sending strategy before proceeding.
The setup includes one DNS step on your side and a configuration step from Delivra.
Create a bounce subdomain under your primary sending domain. For example:
Then create a CNAME record for that subdomain pointing to:
After saving the record, allow time for DNS propagation. Depending on your DNS provider, this may take a few minutes or several hours.
Once your DNS record is live, contact Delivra Support and provide the bounce subdomain you created. Our team will verify the DNS record and will update your site configuration to use the new return path. A test email will be sent to confirm that the Return Path header is correctly set.
After verification, your custom return path will be active for all mailings on the site.
A custom return path is especially useful if:
You enforce a strict DMARC policy such as quarantine or reject.
You want to eliminate “sent on behalf of” messaging in Outlook.
You are focused on strengthening domain based reputation and authentication.
You are preparing for higher volume sending and want tighter control over authentication alignment.
If you are unsure whether this configuration is right for your account, or if you would like help confirming your DNS records, our team is happy to assist.
For questions, reach out to our Support team at support@delivra.com