How To Fix Gmail Message Not Delivered Bounce Errors (2026)
A Gmail bounce message looks alarming, but the error code inside it usually says exactly what went wrong.
Google publishes a list of these codes, and most consumer cases come down to a typo, a full inbox, a size limit or a sending limit.
Use the tables below to read your code and pick the right fix.
Quick answer: read the first digit of the code
| Code starts with | Type | What Google says to do |
|---|---|---|
| 4 (for example 450 4.2.1) | Temporary | Retry the message later |
| 5 (for example 550 5.1.1) | Permanent | Fix the cause before resending |
Google adds “gsmtp” to its SMTP errors, and adds “gcdp” when the error comes from a custom rule set by a Google Workspace administrator.
The address is wrong or the account does not exist
Codes 550 5.1.1, 553 5.1.2, 553 5.1.3 and 553 5.1.7 are addressing errors.
| Code | Meaning | Fix |
|---|---|---|
| 550 5.1.1 | The account does not exist | Check the recipient address for typos or extra spaces |
| 553 5.1.2 | The recipient domain was not found | Check the domain spelling and punctuation |
| 553 5.1.3 | The recipient address is invalid | Correct the address format |
| 553 5.1.7 | The sender address is invalid | Correct the sender address |
The recipient is inactive or their inbox is full
A full inbox on the other side is a recipient problem, not a fault in your Gmail.
| Code | Meaning | Fix |
|---|---|---|
| 452 4.2.2 (temporary) | The recipient’s inbox is full | Have the recipient free up Google Drive storage |
| 550 5.2.1 | The recipient account is inactive | Contact the recipient another way |
| 552 5.2.2 | The inbox is full and inactive | The recipient must free storage |
If you see a similar message about your own account, our guide to Gmail storage that is full with no emails explains how shared storage fills up.
The message or attachments are too big
Code 552 5.3.4 covers size limits.
- If the message exceeds size limits, reduce the message size or attachments.
- If there are too many attachments, reduce the number of attachments.
- If a header or Subject is too long, shorten or remove the oversized header.
Google’s attachment page says the limit on a personal account is 25 MB, and Gmail replaces larger files with a Google Drive link.
You hit a sending limit
Code 550 5.4.5 means the daily user sending limit was exceeded, so wait until the limit resets and then resend.
Code 452 4.5.3 means the policy size per transaction was exceeded or there were too many recipients, so send to fewer recipients per message.
| Message in Gmail | Trigger (per Google) | Wait |
|---|---|---|
| “You have reached a limit for sending mail” | More than 500 emails in a day, or more than 500 recipients in one email | Usually 1 to 24 hours |
| “Messages you sent couldn’t be delivered” | A large number of your emails are invalid or bounce | You may be able to send again after 24 hours |
Our guide on Gmail not sending emails or stuck in Outbox covers the sync and attachment side of sending.
The content or attachment was blocked
Code 552 5.7.0 means Google found a potential security issue in the message or attachment.
Google’s fix is to remove the blocked file type or content and send again.
Executable files such as .exe cannot be attached to Gmail at all.
The message was rejected as spam or for low reputation
Code 550 5.7.1 appears in Google’s list with several different causes.
| Reason listed for 550 5.7.1 | Google’s fix |
|---|---|
| Message is likely unsolicited | Authenticate and reduce spam-like content |
| Very low reputation (IP or domain) | Improve reputation |
| Rate limited | Reduce the sending rate |
| Sending denied or policy prohibits the email | Contact your domain administrator |
If you only send from a personal Gmail account, a 550 5.7.1 message can mean the recipient’s server rejected you, so contact the person another way.
Temporary errors that clear on their own
- 450 4.2.1: the recipient is receiving mail too quickly, so resend later.
- 451 4.3.0 or 421 4.3.0: the server temporarily rejected the message, so retry later.
- 451 4.4.2 or 421 4.4.5: a timeout or busy server, so retry later.
- 421 4.7.0: too many sign-in attempts, or a temporary sign-in problem, so wait and retry.
These codes begin with 4, which Google defines as temporary.
Sign-in and app password codes
If a mail app on your computer or phone shows a code that starts with 53, it is an authentication error.
| Code | Meaning | Fix |
|---|---|---|
| 534 5.7.14 or 534 5.7.90 | Browser sign-in required | Sign in through a web browser, then retry |
| 534 5.7.90 (app password) | An app-specific password is needed | Create and use an app-specific password |
| 535 5.7.80 | Credentials not accepted | Check the username and password |
Less common codes you may see
| Code | Meaning | Fix from Google |
|---|---|---|
| 554 5.4.6 | The message exceeded 50 hops, a mail loop | Fix the routing configuration that causes the loop |
| 554 5.6.0 | The message is malformed | Make the message RFC 5322 compliant |
| 503 5.7.0 | Identity changes are not permitted | Send with the authorized sender identity |
| 530 5.7.0 | Authentication is required | Authenticate before sending |
| 421 4.7.28 or 550 5.7.28 | Unusual rate of unsolicited email | Slow sending and follow Google’s bulk sender guidelines |
Most people with a personal Gmail account will never see these, and they mostly point to a mail app or server setup.
If you send newsletters or business email
Google’s sender guidelines set requirements that apply to all senders as of February 1, 2024.
- Set up SPF or DKIM.
- Use valid forward and reverse DNS (PTR) records.
- Use TLS to transmit email.
- Keep the spam rate in Postmaster Tools below 0.3%.
- Format messages per RFC 5322.
Senders of more than 5,000 messages per day must also set up SPF, DKIM and DMARC, and align the From domain with the SPF or DKIM domain.
Google recommends keeping the spam rate below 0.10% and never reaching 0.30% or higher.
Google also advises increasing volume gradually and avoiding sudden spikes, such as immediately doubling previous volume.
If you use a work or school account
Google notes that sending limits can differ on an account managed by an organization.
For many Cc or Bcc recipients, Google’s bounce guidance for Workspace suggests sending through a group and including only active, correctly spelled addresses.
If a third party cannot receive your mail, Google says the recipient’s administrator may need to update settings to accept it.
If the email never arrives and there is no bounce
A message with no bounce at all is a different problem from the errors above.
If your own inbox is the one missing mail, see why emails are not showing up in Gmail.
Official sources
Codes in this guide come from Gmail SMTP errors and codes, with limits from Limits for sending and getting mail sender requirements from Email sender guidelines, and attachment rules from Send attachments with your Gmail message.