Bounce and error codes
Gmail and Yahoo Error Codes: Quick Reference
A quick lookup for the Gmail and Yahoo bounce codes senders hit most: what each one means, whether it's temporary or permanent, and where to start fixing it.
On this page
Gmail and Yahoo bounce codes come in two kinds. A code starting with 4 (421, 450, 451) is a temporary deferral: your server should retry, and mail often gets through later. A code starting with 5 (550, 553, 554) is a permanent rejection: retrying the same message won't help until you fix the cause. The tables below cover the codes senders hit most, what each means, and where to go next.
How to read a code
A bounce line like 550 5.7.26 has two parts. The first number (550) is the basic SMTP reply. The second (5.7.26) is the enhanced status code, defined in RFC 3463: the first digit repeats the class (4 temporary, 5 permanent), and the middle digit tells you the area. The ones you'll see most:
- x.1.x is about the address (the recipient doesn't exist, the domain is bad).
- x.2.x is about the mailbox (full, disabled).
- x.7.x is security or policy, which is where nearly all deliverability problems live: authentication, reputation, spam filtering.
The number after the last dot is the provider's own detail, and that's where Gmail and Yahoo differ. Always read the text after the code, too. Gmail uses 421 4.7.0 for half a dozen different problems, and only the wording tells them apart. If you need a refresher on finding the bounce in the first place, see how to read a bounce message.
Gmail: temporary deferrals (4xx)
| Code | What it means | Start here |
|---|---|---|
| 421 4.7.0 (low IP or domain reputation) | Gmail doesn't trust your IP or domain right now and is slowing you down | 421 4.7.0 |
| 421 4.7.0 (suspicious content or links) | Something in the message, often a link domain, looks risky | 421 4.7.0 |
| 421 4.7.0 (PTR) / 451 4.7.23 | The sending IP has no reverse DNS, or it doesn't match | 550 5.7.25 |
| 421 4.7.0 (TLS required) | The recipient domain requires TLS and you didn't use it | Enable TLS on your MTA |
| 421 4.7.26 | Neither SPF nor DKIM passed | 550 5.7.26 |
| 421 4.7.27 / 4.7.30 | SPF (4.7.27) or DKIM (4.7.30) didn't pass for a bulk sender | Gmail authentication rate limits |
| 421 4.7.32 | The From domain isn't aligned with the domain that passed SPF or DKIM | Gmail authentication rate limits |
| 421 4.7.29 | A bulk sender didn't use TLS | Gmail authentication rate limits |
| 421 4.7.40 | A bulk sender's domain has no DMARC record | What is DMARC? |
| 421 4.7.28 | An unusual rate of mail, or of unsolicited mail, from your IP, domain or a URL | 421 4.7.28 |
| 450 4.2.1 | That one recipient is receiving mail too fast | Retry; usually not your problem |
| 452 4.2.2 | The recipient's mailbox is full | Retry, then suppress if it persists |
Gmail: permanent rejections (5xx)
| Code | What it means | Start here |
|---|---|---|
| 550 5.1.1 | The address doesn't exist | 550 5.1.1 |
| 550 5.2.1 | The account is inactive (or, in another variant, receiving too fast) | Suppress inactive addresses |
| 552 5.2.2 | Mailbox full and inactive | Suppress |
| 550 5.7.1 (likely unsolicited) | Gmail's filters judged the message to be spam and refused it | Gmail 550 5.7.1 unsolicited |
| 550 5.7.1 (low reputation) | Very low IP or domain reputation, now blocking rather than deferring | Gmail 550 5.7.1 unsolicited |
| 550 5.7.1 (header problems) | Missing or duplicate From, missing Message-ID, malformed headers | Fix the message format (RFC 5322) |
| 550 5.7.25 | No PTR record, or forward DNS doesn't match | 550 5.7.25 |
| 550 5.7.26 | Unauthenticated, an SPF hard fail, or a DMARC p=reject failure | 550 5.7.26 |
| 550 5.7.27 / 5.7.30 / 5.7.32 | The blocking versions of the SPF, DKIM and alignment deferrals | Gmail authentication rate limits |
| 550 5.7.28 | An unusual rate of unsolicited mail from your IP | 421 4.7.28 |
| 550 5.7.40 | Your sending domain has no DMARC record | DMARC record syntax |
A pattern worth knowing: many Gmail problems start as a 421 and turn into a 550 if nothing changes. The authentication codes (4.7.27, 4.7.30, 4.7.32, 4.7.40) and the reputation codes (4.7.0, 4.7.28) all have a blocking twin. A spike in 421s is the warning; take it as one.
Most of the bulk-sender codes trace back to Google's sender guidelines, which apply stricter rules once you send more than 5,000 messages a day to personal Gmail accounts. What changed for Gmail and Yahoo bulk senders covers those rules in one place.
Yahoo and AOL
Yahoo (which also handles AOL mail) documents its errors by family rather than code by code. Its Sender Hub groups them like this:
| Code | What it means | Start here |
|---|---|---|
| 421 / 451 with TS01, TS02, TSS04, TSS05 | Temporary deferral: complaints, unexpected volume, spam-like content or poor IP reputation | Yahoo TS and TSS codes |
| 553 5.7.2 [TSS09] or "permanently deferred" | Yahoo has stopped taking mail from that IP for now | Yahoo TS and TSS codes |
| 550 5.7.9 (unauthenticated) | The message didn't authenticate the way Yahoo requires | Yahoo 550 5.7.9 |
| 554 5.7.9 Message not accepted for policy reasons | Usually a DMARC failure, often on forwarded mail | Yahoo 554 5.7.9 |
| 451 / 554 Unresolvable RFC.5321 or RFC.5322 from domain | The domain in your envelope sender or From header doesn't resolve in DNS | Fix DNS (A or MX, and SOA) for that domain |
| PH* codes | Content blocked for malware, phishing or links to them | Check what's in your outbound queue |
| 554 delivery error | The Yahoo account doesn't exist | Suppress the address |
Yahoo's guidance on the TS family is simple: these are deferrals, your server will retry, and if they persist you can open a Sender Support Request with the full error from your logs. For the 5xx family it says the opposite: don't retry, fix the cause.
If you're blocked at Yahoo across the board rather than seeing one stray code, start with why Yahoo and AOL block email.
What to do with any code
- Check whether it's 4xx or 5xx. Make sure your ESP or MTA treats 4xx as retryable. Suppressing addresses on a 421 throws away good subscribers.
- Read the full text, not just the numbers. Paste the bounce into a note and pick out the IP, domain and any URL it names.
- Group bounces by receiving domain and by code. One code at one provider points at that provider's view of you. The same code everywhere usually points at authentication or a public blocklist.
- Fix the cause the code names. For authentication codes, run your domain through the email checker and check a real message with the header analyzer. For reputation codes, look at what changed in the last few weeks: list source, volume, complaints.
- Watch the trend after the fix. Deferrals that drop off over a few days mean you're on the right track.
When to get help
If the codes keep changing, or you've fixed what the bounce names and the deferrals don't let up after a week or two, it's worth having someone look at your logs and setup with you.
FAQ
Is a 421 from Gmail a bounce?
Not a final one. A 421 is a temporary deferral, and your server should keep retrying. It only becomes a bounce if the retries run out, so a steady stream of 421s still needs fixing.
Do Gmail and Yahoo use the same codes?
They use the same SMTP structure but their own detail codes. Gmail documents specific codes like 5.7.26 and 4.7.28, while Yahoo mostly uses generic codes with its own tags, like [TSS04], in the text.
Where do AOL bounces fit?
AOL mail runs on Yahoo's infrastructure and Yahoo's sender guidance covers both, so AOL bounces follow the Yahoo patterns above.
Why does the same code mean different things?
Because providers reuse generic enhanced codes. 550 5.7.1 at Gmail can mean spam, low reputation or a malformed header, and at other receivers it can mean almost any policy refusal. The text after the code is what tells you which.
Sources
Related guides
- 421 4.7.0: Try Again Later (Gmail Deferrals and Low Reputation)Gmail's 421 4.7.0 is a temporary deferral. Most often it means your IP or domain reputation is very low, or your IP has no valid reverse DNS. Here's the fix.
- 421 4.7.28 / 550 5.7.28: Gmail Detected an Unusual Rate of Unsolicited MailGmail's 421 4.7.28 means it's rate limiting your IP, domain or URL because of volume or spam signals. Pause, slow down, then fix the reputation cause.
- 451 4.7.650: Temporarily Rate Limited Due to IP Reputation (Microsoft)451 4.7.650 means Outlook.com is deferring mail because it doesn't trust your sending IP yet. Slow down, mail engaged users and fix what hurt reputation.
- 550 5.1.1: Recipient Address Rejected, User UnknownA 550 5.1.1 bounce means the recipient's mailbox doesn't exist. It's a permanent failure: fix any typo, or remove the address from your list if it's correct.
- 550 5.1.8: Access Denied, Bad Outbound Sender (Microsoft 365)550 5.1.8 means Microsoft 365 blocked a user from sending, usually because the account was compromised or hit sending limits. An admin must unblock it.
- 550 5.4.1: Recipient Address Rejected, Access Denied (Microsoft)550 5.4.1 means Microsoft 365 didn't find the recipient in that organization's directory. Check the address; if it's right, the recipient's admin must fix it.
Still stuck?
Some deliverability problems take an experienced eye to untangle. Tell me what you're seeing and I'll tell you what I'd check first. The first 30-minute call is free.