Definition
Bounce classification is the system of categorising email delivery failures using SMTP reply codes and enhanced status codes. SMTP codes are three-digit numbers returned by receiving servers during the SMTP conversation or in bounce messages. The 5xx series indicates permanent failures (hard bounces), while the 4xx series indicates temporary failures (soft bounces). Common SMTP codes include 550 (mailbox unavailable), 551 (user not local), 552 (exceeded storage allocation), 553 (mailbox name invalid), 554 (transaction failed), and the 4xx temporary equivalents 450, 451, and 452.
Enhanced status codes provide more granular classification within the SMTP code framework. The format is x.y.z where x specifies the class (2 for success, 4 for temporary failure, 5 for permanent failure), y specifies the subject (1 for addressing, 2 for mailbox, 3 for mail system, 5 for security), and z specifies the detail. Common enhanced codes include 5.1.1 (bad destination mailbox address), 5.2.2 (mailbox full), 4.2.2 (mailbox temporarily full), and 5.7.1 (relay denied or DMARC failure). ISP-specific bounce codes from Gmail, Outlook, Yahoo, and other providers add another layer of classification that senders must interpret for proper bounce handling.
Best Practices
Map bounce codes to automated actions in your bounce processing system. A 5.1.1 (bad address) bounce should immediately suppress the recipient. A 4.2.2 (mailbox full) bounce should retry with exponential backoff up to a maximum number of retries. A 5.7.1 (DMARC failure) should trigger a deliverability investigation, not a suppression.
Differentiate between hard and soft bounces in your list management. Hard bounces indicate permanent delivery failures and the address should be suppressed after the first occurrence. Soft bounces indicate temporary issues; retry for three to seven days before suppressing. A pattern of repeated soft bounces for the same address may indicate a dormant or problematic mailbox.
Maintain a bounce code reference table for each major mailbox provider. Gmail returns 450 4.2.1 for rate limiting, while Yahoo returns 421 4.7.0 for the same condition. Having provider-specific routing ensures appropriate handling. Update the reference table as providers introduce new codes.
Monitor bounce classification distribution over time. A sudden increase in 5.1.1 codes indicates list hygiene issues such as stale data or ineffective confirmation processes. An increase in 4xx codes suggests infrastructure or reputation problems. Classify bounces in your reporting dashboards by code and provider.
Implement suppression per bounce category with different retention periods. Hard-bounced addresses should be permanently suppressed. Addresses with repeated soft bounces should be suppressed for 30 to 90 days before reinstatement consideration. Addresses that cause policy bounces (5.7.x) should trigger a deliverability review, not automatic suppression.
Related Glossary Terms
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.
Email Active Subscriber
An active email subscriber has opened or clicked an email within a defined recency period, typically 30-90 days by industry. Active subscriber rate of 40-60% is typical for healthy email lists.
Email Blacklist
An email blacklist (DNSBL) is a real-time database of IP addresses or domains known for sending spam or unwanted email.
Email Bounce
The return of an undelivered email to the sender, categorized as hard, soft, or transient with distinct handling rules for each.
Email Bulk
Bulk email classification distinguishes mass commercial messages from transactional emails, with specific authentication requirements for senders over 5,000 daily.
Email Bulkhead
Email bulkhead pattern isolates transactional emails from marketing sends using separate IPs, subdomains, and servers. This protects critical deliverability and prevents marketing issues from affecting essential transactional messages.
Frequently Asked Questions
5xx codes indicate permanent delivery failures. The receiving server is stating that the message cannot be delivered and will never be deliverable to that address. 4xx codes indicate temporary failures. The receiving server is stating that the message cannot be delivered right now, but the sender should try again later.
Enhanced status code 5.1.1 means the destination mailbox address does not exist on the receiving server. This is a hard bounce that indicates an invalid email address. The address should be immediately suppressed from all future sends because the mailbox does not exist.
ISP-specific bounce codes extend the standard SMTP and enhanced status code framework with provider-specific subcodes. Gmail, Outlook, and Yahoo each have custom error messages and codes that provide more detail about why a message was rejected. These codes must be interpreted using provider-specific documentation.
Policy bounces with 5.7.x codes indicate that the message was rejected due to a policy enforcement rather than a mailbox problem. Common causes include DMARC policy rejection, SPF failure, DKIM failure, or content policy violations. Policy bounces require investigation of authentication or content issues, not list suppression.
Automated bounce handling should immediately suppress addresses with hard bounce codes (5.1.1, 5.1.2, 5.1.6). Addresses with soft bounce codes should be retried up to three to five times over three to seven days. Addresses with policy bounce codes should trigger a compliance or deliverability review without suppression.