550 5.2.1: the email account that you tried to reach is inactive
The Gmail account you emailed is inactive, so the message bounced. Gmail uses 550 5.2.1 for one more case: a recipient receiving mail at a rate that blocks further delivery.
550 5.2.1 The email account that you tried to reach is inactive.
One of two 5.2.1 messages in Google's Gmail SMTP errors and codes reference, without its closing link.
What 550 5.2.1 means
Google lists two 550 5.2.1 messages. The first says the email account that you tried to reach is inactive. The second says the user you are trying to contact is receiving email at a rate that prevents additional messages from being delivered. RFC 3463 defines X.2.1 as "Mailbox disabled, not accepting messages", which fits both: the mailbox exists but isn't taking mail.
An inactive account usually stays that way. Google's Inactive Google Account Policy says a personal account not used within a 2-year period is considered inactive and Google reserves the right to delete it, and that the policy doesn't apply to accounts set up through work, school or other organizations.
The rate variant is different: the mailbox is active but receiving too much mail. Gmail also has a temporary 450 4.2.1 version of that message. If you see the rate text with a 550, wait before retrying and check you aren't sending the same person many messages in a burst.
Likely causes
- The recipient's personal Gmail account is inactive or was deleted under Google's inactivity policy.
- Rate variant: the recipient is receiving mail faster than Gmail allows.
How to fix it
If you sent the message
- For the inactive text: contact the person another way and ask for a current address.
- Remove inactive addresses from mailing lists; don't keep retrying them.
- For the rate text: slow down, avoid bursts of messages to the same person, and resend later.
If you're the recipient or their admin
- If it's your account, sign in to it: Google counts signing in as activity. For a work or school account, ask your admin.
Frequently asked questions
Can a Gmail account that returns 5.2.1 inactive become active again?
Sometimes. If the owner still has access and the account hasn't been deleted, signing in can make it active again. Google says personal accounts unused for two years can be deleted, so ask the person for a current address.
Should I remove addresses that bounce with Gmail's 550 5.2.1?
Yes, for the inactive-account text. Repeatedly mailing inactive addresses gains nothing and adds to your bounce rate. Remove them, or confirm a new address with the person first.
Sources
- Gmail SMTP errors and codes (Google Workspace Admin Help)
- Inactive Google Account Policy (Google Account Help)
- RFC 3463: Enhanced Mail System Status Codes
Provider messages are quoted as the provider publishes them. Servers can change their wording, so the bounce you received may differ slightly.
Related codes
- 550 5.1.1 550 5.1.1: bad destination mailbox address
- 450 SMTP 450: requested mail action not taken, mailbox unavailable
- 452 4.2.2 452 4.2.2: the recipient's inbox is out of storage space
- 552 5.2.2 552 5.2.2: mailbox full
- 550 5.7.28 550 5.7.28: unusual rate of unsolicited email from your IP
- 550 5.7.24 550 5.7.24: the sending domain's SPF record has suspicious entries
- 553 5.1.7 553 5.1.7: the sender address is not a valid RFC 5321 address
Related guides
Hard bounce vs soft bounce: what's the difference and what should you do?
The difference between hard and soft email bounces, how RFC 3463 status codes classify them, when to retry or remove an address, and how to keep lists clean.
9 min read Running email day to dayHow do you secure email when an employee leaves?
Offboard leavers safely in Microsoft 365 and Google Workspace: block sign-in, revoke sessions, keep or convert the mailbox, forwarding, delegates and devices.
10 min read Running email day to dayEmail deliverability checklist: how to reach the inbox in 2026
A sender checklist for reaching the inbox in 2026: aligned SPF, DKIM and DMARC, reverse DNS, TLS, one-click unsubscribe, spam rates, warming and monitoring.
9 min read