Email bounce management

A bounce is not one thing. Treat it that way.

Separate hard bounces from deferrals, classify DSN and ARF reports, suppress bad addresses and keep provider throttles out of your bounce rate.

A 550 for an unknown mailbox and a 451 from a provider under load both look like failed delivery. They need different responses. Mixing them inflates your bounce rate and hides the real problem.

Hard bounce, deferral, or policy rejection

A hard bounce means the address is not usable now. A deferral is temporary: retry with backoff and watch the provider. A policy rejection may be about authentication, reputation or content. Classify the response before changing suppression or retry settings.

  • 5.1.1 unknown recipient: hard bounce, suppress after a confirmed response.
  • 4.x.x temporary failure: deferral, retry with jitter.
  • 5.7.x policy rejection: investigate domain, IP or content before suppressing.
  • ARF complaint: suppress and treat as a reputation signal, not a bounce.

DSN and ARF sources

Bounce reports can arrive as an SMTP failure, a DSN to the return path, or an ARF complaint to a feedback address. Transmitly normalises these sources and keeps the original SMTP facts so one report does not become three conflicting events.

Suppression that does not fight you

Suppression is checked at intake and again immediately before submission. When a route or domain configuration changes, stale configuration bounces should not keep an address blocked forever. The platform clears its own “recipient domain not handled here” hard bounces when a route is created.

Measure what changed

Track hard-bounce rate by provider, domain and campaign. A bounce spike after a list import is a data problem. A spike after a DNS change is an authentication problem. A spike at one provider may be a directory or policy change.

Questions

Common questions

+Should every 5xx response suppress an address?

No. 5xx responses include mailbox, policy and infrastructure failures. Only permanent address failures should suppress automatically; policy failures need investigation.

+Do you process DSN and ARF reports?

Yes. The inbound listener accepts report mail for the configured bounce and feedback domains, verifies reporter SPF/DKIM where possible, and applies suppression and events.

+Can a suppressed address be restored?

Yes, from the dashboard or API. The audit log records who removed the suppression and when.

+Can I scope webhooks to one domain?

Yes. Webhook endpoints accept an optional set of domain IDs; empty means all domains.

Related

See what the remote MX actually said.

Start free, verify a domain and send a test. Acceptance and delivery evidence stay separate.