A Reply-To of the form reply+{account}@{inbound domain}, set on customer email when an inbound domain is configured. It turns a shared sending domain from 'we can send but not receive' into a working two-way mailbox for every account.
Also called: customer replied and it went nowhere · reply-to · shared sending domain · email replies not coming back
- 1The account id is encoded into the local part of the reply address
- 2The inbound resolver checks that first — a VERP address wins outright because it names the account, so nothing is shared
- 3It is only emitted when an inbound domain is configured, because a Reply-To pointing at a domain with no inbound route would bounce
Several businesses share one sending domain, which means the domain alone cannot say which of them a reply belongs to — and guessing would put one builder's customer reply into another builder's inbox. Rather than guess, unresolvable replies were held for a human, which left accounts on the shared domain able to send but not receive. Outbound email now carries a reply address that names the account, so a reply can be filed with certainty and every account on a shared domain has a working two-way mailbox.
- Replies unroutable on a shared sending domain
- Reply addresses on domains with no inbound handling
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →