CONSOLE
Loading
Keep bounce rates safely below the 2.0% industry threshold, decode SMTP 5xx and 4xx status codes, and protect your domain reputation against ISP blacklists.
To fix a high email bounce rate, maintain an overall bounce rate strictly below 2.0% by enforcing real-time email syntax and MX verification at signup, implementing confirmed double opt-in, immediately suppressing all permanent hard bounces (SMTP 5xx), retrying temporary soft bounces (SMTP 4xx) with exponential backoff queues, and purging subscribers who haven't opened emails in over 90 days.
Every time your application sends an email to an invalid, expired, or non-existent address, the destination Mail Transfer Agent (MTA) records a delivery failure.
To major mailbox providers like Google, Microsoft, and Yahoo, high bounce rates are the single strongest algorithmic signal that a sender is using unverified lists, scraped databases, or compromised forms. This triggers a destructive chain reaction:
ISPs respond with 451 4.7.500 temporary rejections, slowing dispatch speeds from thousands per minute down to single digits.
Legitimate emails to active, engaged customers are automatically diverted away from the inbox into the Spam or Junk folder.
Spamhaus, Barracuda, or ISP-internal filters list your IP and domain, permanently rejecting all transactional and marketing dispatches.
Under RFC 3463 and RFC 5321, email delivery failure codes are divided into two distinct categories:
| Bounce Type | SMTP Code | Typical Reason | Required System Action |
|---|---|---|---|
| Hard Bounce | 550 5.1.1 |
User unknown / Mailbox does not exist | Immediate permanent suppression. Never attempt redelivery. |
| Hard Bounce | 550 5.1.2 |
Host unknown / Domain does not have MX records | Permanent suppression and database email format sanitization. |
| Hard Bounce | 554 5.7.1 |
Rejected due to sender blacklist or policy rejection | Investigate IP/domain reputation; verify SPF/DKIM/DMARC. |
| Soft Bounce | 452 4.2.2 |
Mailbox full / Quota exceeded | Retry with exponential backoff for 48 hours; suppress if it persists. |
| Soft Bounce | 451 4.4.1 |
No answer from host / Connection dropped | Hold in spool queue and retry after 15 to 30 minutes. |
| Soft Bounce | 450 4.7.1 |
Greylisted / Rate limited by recipient server | Slow down sending concurrency and retry after 5 to 10 minutes. |
What percentage of bounces is acceptable? Here is how mailbox providers evaluate your sending health:
Never let a user submit a typo like user@gnail.com or user@hotmial.com. Run a quick MX lookup before storing emails in your database:
// Node.js MX Record Validation
const dns = require('dns').promises;
async function validateEmailDomain(email) {
const domain = email.split('@')[1];
try {
const mxRecords = await dns.resolveMx(domain);
return mxRecords && mxRecords.length > 0;
} catch (err) {
return false; // Domain has no valid mail exchangers
}
}
Send a verification link to the recipient's inbox before adding them to your permanent notification list. This eliminates bot registrations and fake contact entries at zero cost.
When an email returns an SMTP 5xx response code, mark the record in your database as suppressed = true immediately. Attempting to email the same non-existent mailbox a second time results in harsh penalties from ISP reputation algorithms.
For soft bounces (e.g. 452 Mailbox Full), configure your MTA to retry delivery with exponential backoff: attempt retry at 5 minutes, 15 minutes, 1 hour, 6 hours, and 24 hours. If it fails for 72 consecutive hours, convert the soft bounce into a permanent suppression.
Abandoned corporate and free webmail inboxes are eventually deactivated by providers and converted into spam traps. Automatically unsubscribe or isolate recipients who haven't opened or clicked an email in 90 to 180 days.
When using PhotonRelay, you can receive real-time webhook payloads for all hard and soft bounce events:
// Webhook Payload Example: email.bounced
{
"event": "email.bounced",
"timestamp": "2026-11-16T21:00:00Z",
"recipient": "invalid-user@example.com",
"bounce_type": "hard",
"smtp_code": 550,
"diagnostic_code": "550 5.1.1 <invalid-user@example.com>: Recipient address rejected: User unknown",
"message_id": "msg_01k9d82f7h3j4l"
}
PhotonRelay automatically isolates hard bounces, maintains multi-tenant suppression lists, and includes built-in circuit breakers that prevent dirty lists from damaging your domain reputation.
Trademark Notice & Nominative Fair Use: All third-party trademarks, logos, and service marks (SendGrid®, Mailgun®, Amazon SES®, Postmark®, Resend®, Brevo®, SMTP2Go®, SparkPost®) are property of their respective owners and used under 15 U.S.C. § 1115(b)(4).
Photon Console is independent and not affiliated with or endorsed by these providers. Pricing and plan details compiled from public sources as of November 2026. Read full legal disclaimer →