SMTP Error 550 & Common Bounce Codes Explained

A bounce message with 550 in it is one of the most common - and most misunderstood - errors in email. A 550 is a permanent failure: the receiving server has decided your message will not be delivered, and retrying will not help. But 550 is a family of errors, not one problem, and the three-digit enhanced code that follows it tells you exactly what went wrong. Here is what each common bounce code means, what causes it, and how to fix it.

What SMTP Error 550 Actually Means

SMTP replies come as three-digit codes. Anything in the 5xx range is a permanent ("fatal") failure - the server is rejecting the message outright. Anything in the 4xx range is a temporary ("transient") failure that the sending server will retry. A bare 550 generically means "requested action not taken: mailbox unavailable," but modern servers attach an enhanced status code (like 5.1.1 or 5.7.1) that pinpoints the real cause.

Common Bounce Codes at a Glance

550 5.1.1 - Recipient Doesn't Exist

This is the most frequent 550. The address is invalid - a typo, a former employee, or a made-up address from an unverified list. The fix is list hygiene: verify addresses before you send. Repeated 5.1.1 bounces are a red flag to inbox providers that you are working from a stale or purchased list, which quietly damages your sender reputation and pushes even your valid mail toward spam.

550 5.7.1 - Blocked by Policy

A 5.7.1 (and Gmail's common 550-5.7.1) means the recipient server accepted that the address exists but refused the message on policy grounds. Causes include failing SPF/DKIM/DMARC authentication, a poor sending reputation, missing an unsubscribe header on bulk mail, or being listed on a blacklist. The fix depends on the cause: lock down authentication first, then check your reputation and blocklist status.

554 - Transaction Failed

A 554 is a blunt, catch-all rejection - the server refused the whole transaction. In practice it usually means your sending IP or domain is on a blacklist like Spamhaus, or the content tripped a spam rule. Look up your IP and domain on the major blocklists, request delisting if you are on one, and fix whatever behavior got you listed before you resume sending.

421 and 451 - Temporary Failures

These 4xx codes are not permanent. A 421 means the service is unavailable or you are being throttled for sending too fast; a 451 often signals greylisting - the server is deliberately deferring an unknown sender and asking you to retry, which legitimate mail servers do automatically. You usually do not need to act on a single 4xx, but a flood of 421s means you are sending too aggressively and should slow down.

Hard Bounce vs Soft Bounce

The 5xx / 4xx split maps neatly onto a distinction you will hear constantly: a hard bounce is a permanent 5xx failure - the address is invalid, blocked, or refused, and it will never accept your mail. A soft bounce is a temporary 4xx failure - a full mailbox, a server hiccup, or throttling - that often clears on retry. The reason the difference matters is that inbox providers weigh them very differently: hard bounces are the ones that seriously damage your reputation, because they signal a sender who does not verify their list. Soft bounces are noise you can usually tolerate, but if the same address soft-bounces repeatedly for days, treat it as effectively dead and remove it.

A practical habit is to read the full bounce message rather than just the code. The enhanced status code and the human-readable text after it (Gmail, for example, often links to a support page explaining the exact rejection) usually name the real problem - authentication, reputation, or a bad address - so you fix the cause instead of guessing.

How Bounces Hurt Deliverability

Every hard bounce is a negative signal. A rising bounce rate tells Gmail and Outlook that you are not managing your list, and they respond by filtering more of your mail - so bounces do not just fail individually, they degrade placement for everything you send. Keeping bounces under about 2% is a practical target for healthy sending.

How to Prevent 550 Bounces

1. Verify every address before sending to kill 5.1.1 bounces at the source.
2. Set up SPF, DKIM, and DMARC correctly so you never bounce on 5.7.1 authentication failures.
3. Check your IP and domain against major blacklists regularly, and delist fast if you appear.
4. Ramp sending volume gradually instead of spiking - erratic velocity triggers 421 throttling.
5. Warm up new mailboxes so your reputation is strong before real campaigns start.

Fix the Root Cause: Reputation

Most policy-based 550s trace back to one thing - a sending domain that inbox providers do not yet trust. MailPilot warms your mailbox across 8,400+ real inboxes, builds the positive engagement history that prevents 5.7.1 rejections, and monitors inbox placement so you catch reputation problems before they turn into bounces. See how automated warmup works - plans are flat: Free, $9, $25, or $59. Warm up your inbox free →