Topic · Deliverability
Soft bounce
A soft bounce is a temporary delivery problem such as an unavailable service, capacity issue or transient rate limit.
How it works
Mail transfer systems generally retry temporary failures during an allowed delivery window.
What can go wrong
Treating every soft bounce as transient forever can disguise reputation blocks or persistent configuration problems.
What to check or do
Inspect enhanced SMTP status codes and apply bounded retries with escalation for repeated failures.
How to investigate Soft bounce
- Signal to investigate
- Delivery attempts defer for several hours with temporary SMTP status codes.
- Evidence to collect
- Capture SMTP 4xx replies, retry timestamps, queue age and recipient-domain concentration.
- Common wrong conclusion
- A 4xx deferral is not equivalent to a permanently invalid recipient.
How to interpret the evidence
Temporary errors may mean rate limiting, greylisting, unavailable infrastructure or quota conditions. Endless retry can worsen reputation and waste queue capacity.
What to change and how to verify it
Use bounded exponential retry, reduce pressure during throttling and alert when queue age approaches the delivery SLA.
Put this into practice
Run a focused check, then explore protection if your domain needs it.