Email Bounce Reasons Explained: Hard, Soft, and Everything In Between

When an email cannot be delivered, the receiving server sends back a bounce message — a non-delivery report (NDR) that tells you why. Understanding bounce reasons is essential for maintaining a healthy sender reputation and keeping your list clean.

Hard bounces vs. soft bounces

The terms "hard bounce" and "soft bounce" describe how likely a delivery failure is to be permanent.

Hard bounces

A hard bounce means permanent failure. The address does not exist, the domain does not accept mail, or the receiving server has permanently rejected this sender. Common causes:

• User does not exist (550 5.1.1): The username portion of the address is not registered at that domain
• Domain does not exist (550 5.1.2): The domain has no MX records or does not exist in DNS
• Address is rejected: A domain-level block on all mail from your address or domain

When you receive a hard bounce, remove the address from your list immediately. Continuing to send to hard-bounced addresses damages your sender reputation and signals to mailbox providers that your list is not maintained.

Soft bounces

A soft bounce is a temporary failure. The address is valid, but delivery failed for a transient reason:

• Mailbox full (452 4.2.2): The recipient's mailbox has exceeded its storage quota
• Server temporarily unavailable (421 4.3.0): The receiving server is down or overwhelmed
• Rate limit exceeded (421 4.7.0): The receiving domain is throttling connections from your IP
• Message too large (552 5.3.4): Your message exceeds the server's size limit

For soft bounces, most sending systems retry delivery over a period of hours or days. If the condition persists and retries exhaust, the message expires as a permanent failure.

SMTP status codes

SMTP response codes follow a three-digit structure: the first digit indicates success (2xx), temporary failure (4xx), or permanent failure (5xx).

2xx — Success

• 250 OK: Message accepted for delivery
• 251 User not local: The address will be forwarded

4xx — Temporary failure (soft bounce territory)

• 421: Service unavailable, try again later
• 450: Mailbox unavailable, try again
• 451: Local processing error
• 452: Insufficient system storage

5xx — Permanent failure (hard bounce territory)

• 500: Syntax error
• 501: Syntax error in parameters
• 503: Bad sequence of commands
• 550: Mailbox unavailable — the most common hard bounce code
• 551: User not local, do not retry
• 552: Exceeded storage allocation
• 553: Mailbox name not allowed
• 554: Transaction failed

The enhanced status codes (the X.X.X portion after the numeric code) provide more detail and are often more useful than the base code alone.

Common bounce messages and what they mean

"550 5.1.1 The email account that you tried to reach does not exist"

The address does not exist at the recipient domain. This is the most common hard bounce. Remove the address.

"550 5.7.1 Message rejected due to spam content"

Your message triggered a content filter. This is a delivery failure, not a bounce from the address being invalid. Review your message content and sending patterns.

"550 5.7.26 This message does not have authentication information"

Your domain's SPF, DKIM, or DMARC configuration is missing or failing. The message was rejected because it could not be authenticated.

"452 4.2.2 Mailbox full"

The recipient's mailbox is at capacity. Retry after some time. If this persists for the same address, the account may be abandoned — consider sunsetting it after several attempts.

"421 4.7.0 Try again later"

The receiving server is rate-limiting you. Your sending IP or domain may be on a greylist, or you may be sending too fast to that domain. Back off and retry.

Spam trap hits

Not all bounces come from real addresses. Spam traps — addresses maintained specifically to catch spammers — look like normal addresses but never generate real bounces until your IP or domain is flagged. Hitting spam traps is a serious reputation problem that requires list hygiene work to resolve.

How bounce rates affect deliverability

Inbox providers track bounce rates per sending IP and domain. High bounce rates signal that your list was not obtained through legitimate opt-in, that you are not cleaning your list, or that you purchased contact lists.

Acceptable bounce rates vary by provider, but a general rule:

• Hard bounce rate below 2% is generally acceptable
• Hard bounce rate above 5% is a warning sign
• Hard bounce rate above 10% will likely trigger rate limiting or blocking

Reducing your bounce rate

Use confirmed opt-in (double opt-in)

Sending a confirmation email before adding someone to your list catches mistyped addresses before they become bounces. A confirmed opt-in list has dramatically lower bounce rates than a single opt-in one.

Validate email addresses at point of collection

Client-side format validation catches obvious typos. An email verification API call at signup can catch addresses that are syntactically valid but do not exist, before they ever enter your sending list.

Sunset unengaged subscribers

Addresses that have not opened or clicked in 12-18 months are at higher risk of having been abandoned or converted to spam traps. Remove or suppress them proactively.

Monitor and act on bounces promptly

With Rovela, every bounce is recorded on the delivery event for that message, including the full SMTP status code and the bounce message text. The suppression list is updated automatically for hard bounces — addresses that hard-bounced will not receive future sends, protecting your reputation.

Check your infrastructure

Authentication failures (SPF, DKIM, DMARC) can cause otherwise valid addresses to bounce with a 550 5.7.x code. Verify your DNS records are correct and that your sending IP is authorized in your SPF record.