Who this applies to#
- Use the soft-bounce classification when the receiving system describes a transient condition rather than a permanent invalid destination
What Soft bounce requires#
- Bound retries and monitor repeated failures instead of treating a temporary response as unlimited permission to resend
Amazon SES
SES describes soft bounces as temporary failures and may retry before returning a final result
What this does not require#
- One soft bounce does not by itself prove that the destination is permanently invalid
Common mistakes#
- Calling every bounce permanent
- Retrying indefinitely
- Ignoring repeated temporary failures
Soft bounce checklist#
- Read the response
- Classify permanence
- Bound retries
- Escalate repeated failure
Commonly confused with#
OnVoard's take#
Bound retries for a soft bounce and watch repeated failure. A temporary classification is not permission to resend indefinitely.