Skip to content

SMTP Error Codes Explained: 421, 535, 550, 554 and More

What the code in a bounced email means — 421, 450, 452, 530, 535, 550 5.1.1, 550 5.7.1, 550 5.7.26, 552, 554 — and how to fix it, for Gmail, Microsoft 365, Outlook.com and Yahoo.

When an email can't be delivered, the bounce message (also called a non-delivery report, NDR or DSN) contains a short code such as 550 5.1.1. That code tells you whether the problem is temporary or permanent, whose side it's on, and usually exactly what to fix. This guide explains how to read the codes and lists the ones Gmail, Microsoft 365, Outlook.com and Yahoo return most often.

How to read an SMTP error code

Most bounces show two codes side by side:

550 5.1.1 The email account that you tried to reach does not exist.
  • The three-digit reply code (550) is the basic SMTP answer. The first digit is what matters most: 4 means a temporary failure, 5 a permanent one.
  • The enhanced status code (5.1.1) adds detail in three parts: class.subject.detail (RFC 3463).
First digit (class)MeaningWhat happens next
2SuccessDelivered.
4Temporary failure — the message is valid, but can't be delivered right nowThe sending server normally retries on its own. You only see a bounce if retries run out.
5Permanent failure — resending the same message won't helpSomething has to change first: the address, the message, or the sender's setup.

The middle number of the enhanced code says where the problem is:

SubjectAreaUsually fixed by
x.1.xAddressing — the sender or recipient addressThe sender (check the spelling)
x.2.xThe recipient's mailbox — full, disabled, too small for the messageThe recipient
x.3.xThe receiving mail systemThe recipient's administrator
x.4.xNetwork and routing — DNS, connections, delaysWhoever runs the servers involved
x.5.xThe mail protocol itselfThe sending software
x.6.xMessage content or formatThe sender
x.7.xSecurity and policy — authentication, spam filtering, permissionsThe sender's settings or domain records

The most common codes and what to do

CodeWhat it meansWhat to do
421 4.7.0Temporary rejection. Gmail uses it for “try again later”, a required TLS connection, or a sender with very low reputation.Usually wait — the server retries. If it repeats, check your sending domain's authentication and reputation.
421 4.7.28Gmail detected an unusual rate of mail from your IP address or domain and is rate-limiting it.Slow down. Check whether an account or website form is sending spam.
450 4.2.1The recipient is receiving mail too quickly to accept more right now.Nothing on your side; the message is retried.
452 4.2.2The recipient's inbox is out of storage space (Gmail).The recipient needs to free up space. Let them know another way.
454 4.7.0Temporary authentication failure.Try again shortly.
530 5.7.0Authentication required — or, from Gmail, “Must issue a STARTTLS command first”.Turn on outgoing-server authentication, and use port 587 with STARTTLS or 465 with SSL/TLS.
535 5.7.8Username and password not accepted.The password is wrong, or the provider needs an app password or OAuth sign-in instead of your normal password.
550 5.1.1The recipient's address doesn't exist.Check the spelling. Don't keep resending.
550 5.7.1Delivery not authorised. A catch-all for policy blocks: suspected spam, low reputation, missing headers, or a recipient who doesn't accept mail from you.Read the text after the code — it names the reason.
550 5.7.25Gmail: the sending IP address has no matching reverse DNS (PTR) record.The server's owner needs to add a PTR record that matches its host name.
550 5.7.26Gmail: the message is unauthenticated — it failed SPF with -all, or failed the sender domain's DMARC policy.Fix SPF, DKIM and DMARC for the sending domain. Check them here.
552 5.2.2The recipient's mailbox is full. (Microsoft uses the same code for a different problem — see below.)The recipient has to free up space.
552 5.2.3The message is larger than the recipient's mailbox allows.Send a link to the file instead of attaching it.
554 5.6.0Gmail: the message is malformed.Usually a bug in the sending software or a script that builds the message.

Gmail and Google Workspace

Gmail's bounces always include the reason in plain words after the code, and many of them point to the same three causes:

  • Authentication. 550 5.7.26 means your domain's SPF, DKIM or DMARC didn't hold up. Since 2024, Gmail requires SPF or DKIM from every sender, and all three from anyone sending 5,000 or more messages a day.
  • Reputation and rate. 421 4.7.0 and 550 5.7.1 with “very low reputation”, or 421 4.7.28 “unusual rate”, mean Gmail is treating the traffic as suspicious. Check for a compromised account or a contact form being abused before anything else.
  • Message format. Several 550 5.7.1 variants reject messages that aren't RFC 5322 compliant — no valid From address, more than one From header, a missing Message-ID, or duplicate headers. These come from website code or scripts, not from normal mail apps.

If you're the one who can't send through smtp.gmail.com and you see 535 5.7.8 “Username and Password not accepted”, see Gmail SMTP settings for the sign-in options.

Microsoft 365 and Outlook.com

Microsoft's non-delivery reports use their own detailed enhanced codes:

CodeMeaning
5.1.1, 5.1.10The recipient address doesn't exist or wasn't found.
5.1.8Your account has been blocked for sending spam — usually because it was compromised. Secure the account, then contact your administrator.
5.2.2You exceeded a sending limit (recipient or message rate). This is Microsoft's own use of the code; elsewhere 5.2.2 means the recipient's mailbox is full.
4.4.7The message expired in the queue before it could be delivered.
5.4.1Relay access denied: the receiving server doesn't accept mail for that domain, often because of a DNS or mail-server configuration problem.
5.7.1Delivery not authorised — the sender isn't allowed to send to that recipient, or the client wasn't authenticated.
5.7.23The message failed the receiving system's SPF check.
5.7.57A device or app sending through smtp.office365.com wasn't authenticated. See Microsoft 365 SMTP settings.
5.7.124, 5.7.133, 5.7.134The group or mailbox you wrote to only accepts mail from certain senders, or only from inside its organisation.
5.7.509The sender's From domain didn't pass DMARC.
5.7.501, 5.7.511The sending account or IP address has been banned for spam.

Yahoo

Yahoo groups its errors rather than giving one meaning per code:

  • 421 or 451 — a temporary problem; retry later. Messages marked TS01, TS02 and similar are temporarily deferred, typically because of complaints, spam-like content, poor IP reputation or unusual traffic.
  • 553 or 554 — a permanent problem; don't retry. Causes include failing DKIM or DMARC, an IP listed by Spamhaus, unacceptable content, or a recipient that doesn't exist — for example “554 delivery error: dd This user doesn't have a yahoo.com account”.

What to do with a bounce

  1. Look at the first digit. A 4 usually fixes itself; wait a few hours before doing anything. A 5 won't.
  2. Read the text after the code. Gmail and Microsoft both say the reason in plain words.
  3. Check the address for any 5.1.x code.
  4. Check your domain's records for any authentication-related 5.7.x code, with the SPF, DKIM & DMARC Checker.
  5. If the bounce says your own mailbox or account is blocked, change your password and check for forwarding rules you didn't create — compromised accounts are the most common cause.

How this guide was checked · October 2026

Verified against 7 official sources

Every step, setting and limit in this guide was checked against the provider’s own documentation on support.google.com, learn.microsoft.com, senders.yahooinc.com and 2 more. Anything we couldn’t confirm was left out.

  1. 01 Google: Gmail SMTP errors and codes support.google.com
  2. 02 Microsoft: Email non-delivery reports and SMTP errors in Exchange Online learn.microsoft.com
  3. 03 Yahoo: SMTP error codes senders.yahooinc.com
  4. 04 IETF RFC 3463: Enhanced Mail System Status Codes rfc-editor.org
  5. 05 IETF RFC 4954: SMTP Service Extension for Authentication datatracker.ietf.org
  6. 06 IETF RFC 5321: Simple Mail Transfer Protocol rfc-editor.org
  7. 07 Google: Email sender guidelines support.google.com

Questions

Frequently asked questions

What is the difference between 4xx and 5xx SMTP errors?

A 4xx code is a temporary failure: the sending server retries on its own, and the message often gets through later. A 5xx code is permanent: resending the same message won't help until something changes.

What does 550 5.1.1 mean?

The recipient's address doesn't exist at that provider. Check the spelling of the address; if it's correct, the account may have been closed.

What does 550 5.7.26 mean in Gmail?

Gmail rejected the message as unauthenticated: it failed SPF with a -all policy, or failed the sending domain's DMARC policy. The sending domain needs working SPF, DKIM and DMARC.

What does 535 5.7.8 mean?

The server didn't accept the username and password. Re-enter them, and check whether the provider requires an app password or its own sign-in (OAuth) instead of your normal password.

What does 552 5.2.2 mean?

Normally that the recipient's mailbox is full. In Microsoft 365 non-delivery reports, 5.2.2 instead means the sender exceeded a sending limit.

Should I resend after a 421 error?

Usually not straight away. 421 is temporary and the sending server retries automatically. If you get a final bounce after retries, wait a while and try again.

Related guides

Keep reading