Definition
An email bounce occurs when a sent message is rejected by the recipient's mail server before reaching the inbox. Bounces fall into three categories. Hard bounces are permanent rejections caused by invalid email addresses (the account does not exist, the domain does not resolve, the mailbox is full in a non-retryable way). Soft bounces are temporary delivery failures such as a full mailbox (over-quota) or an out-of-office auto-reply that is technically a bounce. Transient bounces are server-level issues like timeouts or greylisting where the ISP asks the sender to retry later.
Bounce handling is critical to sender reputation. ESPs and ISPs track bounce rates; a hard bounce rate consistently above 2 to 5 percent can result in account suspension or blacklisting. Automated workflows must parse bounce codes (SMTP status codes like 550, 554, 450) and classify each bounce into the correct category to determine whether to suppress, retry, or flag the address for review.
Best Practices
Suppress hard bounces immediately and permanently. Never retry sending to an address that returned a 5xx SMTP response indicating the mailbox does not exist. Each retry increases your bounce rate and damages your sender reputation with that ISP. Configure your ESP to automatically move hard-bounced addresses to a suppression list.
Implement a retry schedule for soft bounces with decreasing frequency. Retry after 15 minutes, then 1 hour, then 4 hours, then 24 hours, and drop the address after 72 hours of consecutive soft bounces. ISPs like Gmail consider repeated rapid retries as abusive behavior. Use exponential backoff with a maximum of 4 to 6 retry attempts before suppression.
Parse SMTP bounce codes from both the envelope (DSN) and the body of the bounce message. A bounce may include diagnostic codes like "550 5.1.1" (user unknown) or "450 4.2.2" (mailbox full). Different ESPs and ISPs format these messages differently. Use a bounce parsing library (such as bounce-api or mail-bounce-detector) to normalize the response and classify it reliably.
Monitor your global bounce rate per campaign and per ISP. A sudden spike in soft bounces from a single ISP (e.g., Outlook.com returning 450 errors on 20% of deliveries) may indicate the ISP is rate-limiting your IP. In that case, throttle your send rate rather than continuing to blast and accumulating bounces. Separate ISP-level issues from list-quality issues.
Related Glossary Terms
AI Content Detection
AI content detection refers to the growing ability of email clients, spam filters and consumers to identify machine-generated email copy. It matters for deliverability, trust and engagement in an era of mass-produced AI marketing email.
Batch Sending
Batch sending is the practice of delivering a single email campaign to a large list in groups or waves rather than all at once.
Bounce Classification
Bounce classification uses SMTP codes (550, 551, 552, 553, 554, 450, 451, 452) and enhanced status codes to categorise permanent and transient delivery failures.
Complaint Rate
Complaint rate is the percentage of delivered emails that recipients mark as spam, a key indicator of sender reputation and list quality.
DMARC Alignment
DMARC identifier alignment determines whether the domain in the From header matches the domains used in SPF and DKIM authentication. Strict or relaxed.
Acceptance Rate
Acceptance rate is the percentage of emails submitted for delivery that are accepted by the recipient's mail server, representing the first deliverability checkpoint before inbox placement is determined.
Frequently Asked Questions
An auto-responder (out-of-office, vacation message) is not a bounce. It is a successful delivery followed by an automated reply. Most ESPs classify auto-responders as delivered plus an auto-reply event. They do not count toward your bounce rate. Do not suppress addresses that only return auto-responders.
SMTP code 550 with enhanced status code 5.1.1 (mailbox does not exist) is the most common hard bounce. Other hard bounce indicators include 521 (server does not accept mail), 550 5.1.2 (host not found), and 550 5.4.1 (no answer from host). Each ESP may map these slightly differently.
Clean hard bounces after every send. Run a full list hygiene process monthly: remove addresses that have bounced hard in the last 3 months, recency-check addresses that have not engaged in 6 months, and validate new addresses at point of collection with a real-time email verification API.
Rarely. If an address is suppressed for a hard bounce (mailbox does not exist), it is almost certainly a typo or abandoned account. Re-engaging it requires explicit re-subscription through a confirmed opt-in. Do not automatically retry hard-bounced addresses after any time period.
A bounceback loop occurs when bounce messages are sent to an address that itself bounces, creating an infinite cycle of bounce messages. This happens when the bounce handling mailbox is not properly configured. Always use a dedicated bounce processing address with appropriate suppression rules and never use that address as a reply-to or from address.