What is a soft bounce?
A soft bounce is a temporary delivery failure: the receiving server couldn't take the message right now but might later. The sending server keeps the message and retries, and only gives up after repeated failures.
A soft bounce comes from a temporary error, a reply code starting with 4. The address is probably real; something about this moment isn't working. The mailbox is full, the server is overloaded, it's limiting how fast you can send, or it's deliberately deferring senders it doesn't know yet.
Sending servers queue the message and retry on a schedule. The SMTP standard (RFC 5321) suggests a give-up time of at least four to five days, though many sending platforms stop sooner. If the retries run out, the message bounces for good.
Common soft-bounce replies
| Code | Typical cause | Usually clears |
|---|---|---|
421 4.7.0 | Server busy, or rate-limiting your sending IP | Within minutes or hours; slow down if it keeps happening |
450 4.2.1 | Mailbox temporarily not accepting mail | On a later retry |
451 4.7.1 | Greylisting or a temporary policy check | After the server's wait period, often minutes |
452 4.2.2 | Mailbox full (over quota) | When the owner clears space, if they ever do |
452 4.5.3 | Too many recipients in one transaction | Immediately, by sending in smaller batches |
Codes and wording vary by provider. The first digit decides: 4 means try again later, 5 means stop.
When a soft bounce should be treated as hard
A one-off soft bounce isn't a reason to remove anyone. A pattern is. An address that soft-bounces campaign after campaign, especially with a full mailbox, is usually an abandoned inbox. Many sending platforms suppress an address automatically after a few consecutive soft bounces.
Rate-limit and greylisting deferrals are different: they say nothing about the address. If lots of addresses at one provider soft-bounce at once, slow down your sending to that provider instead of cleaning the list. See /glossary/greylisting.
How soft bounces show up in verification
Full mailbox
MailVet returns risky with reason mailbox_full. The mailbox exists, so hold the address and retry later.
Greylisted or no answer
Returned as unknown with reason no_response. It costs nothing, and re-running later usually settles it.
Busy or rate-limited server
Also unknown and free, so a temporary problem on their side never becomes a permanent "undeliverable" on yours.
Soft bounce questions
Do soft bounces hurt sender reputation?
Occasional ones don't. Repeated soft bounces to the same dead mailboxes, or a wave of rate-limit deferrals because you sent too fast, are signals providers notice. Fix the pattern: remove long-term full mailboxes and slow down where you're being deferred.
How many times should I retry a soft bounce?
Your sending server handles retries for each message on its own. Across campaigns, a common approach is to suppress an address after it soft-bounces on several sends in a row. Check how your sending platform handles it; many do it automatically.
Is a full mailbox a hard or soft bounce?
Usually soft, sent as a temporary 452 4.2.2 error. Some servers report it as a permanent 552 instead. Either way, an inbox that stays full for weeks has probably been abandoned.
Can email verification predict soft bounces?
Partly. It can see a full mailbox, or a server that isn't answering, at the moment of the check. It can't predict a rate limit you'll hit later by sending too much too fast.
Separate the temporary from the permanent
Every MailVet result says why it came back the way it did, so a slow server is never mistaken for a dead address. Unknown results are free.