Gmail "550 5.2.1 The email account that you tried to reach is disabled"

What it means

The address exists at Gmail or Google Workspace, but the account behind it cannot receive mail right now. Google refused your message. The bounce usually looks like this:

550-5.2.1 The email account that you tried to reach is disabled. Learn more at
550 5.2.1  https://support.google.com/mail/?p=DisabledUser

Google also uses the same 5.2.1 code with the wording "The email account that you tried to reach is inactive".

This is a problem on the recipient's side. It is not about your SPF, DKIM, content or reputation, and nothing in your DNS can change it. It differs from "550 5.1.1": the address does not exist, where the address is unknown, and from "552 5.2.2": the mailbox is full.

Why it happens

Google does not tell senders why an account is disabled. The usual reasons are:

• Google disabled the account, for example for a terms-of-service violation or suspected compromise.
• A Google Workspace admin suspended the user, often when an employee leaves the company.
• The account was inactive for a long time. Google's inactive account policy allows it to delete personal accounts that have not been used for two years; an address on an old list can be in this state.
• The owner closed Gmail on that account or is in the middle of an account recovery.

The state can be temporary (a suspended user who is restored) or final. You cannot tell from one bounce.

How to check

1. Read the full bounce and make sure the code is 5.2.1 with "disabled" or "inactive". Different 5.2.x wording means a different problem.
2. Count how many addresses bounced this way. One address is normal life. Dozens in one campaign mean your list contains many old addresses.
3. Check your sending tool's suppression list. Most providers add the address automatically, so later sends fail inside the provider (for example Mailgun 605) instead of reaching Google.
4. Rule out a problem on your side anyway: send a test to the unique address on the Delivmail home page. If SPF, DKIM, DMARC and blacklists are fine, the bounce really is about the recipient account.

How to fix it

You cannot reactivate someone else's account. What you can do:

1. Stop sending to the address. Treat it like a hard bounce. Mark it as undeliverable in your database or CRM. Repeated sends to disabled accounts count against your sender reputation at Gmail.
2. Reach the person another way if the email matters (phone, another address, a message in your app) and ask for a working address.
3. For a business contact, the person may have left the company: contact the company through its main address.
4. Clean your list if many addresses are affected. Remove contacts who have not opened or clicked for a long time, and run a re-engagement campaign before removing the rest; see inactive subscribers: re-engage or remove them and clean your mailing list after a high bounce rate.
5. Do not retry in a loop. A 550 is permanent; your server will not retry, and you should not force it.

If the person says the account works

Ask them to sign in to Gmail in a browser and check for an alert about their account. Once they confirm it is restored, remove the address from your provider's suppression list and send one message. If it bounces again with 5.2.1, the account is still disabled.

Check that it is fixed

There is nothing to fix on your server, so success means two things: your application no longer sends to the disabled address, and new bounces of this type stay rare. After a list clean-up, watch your bounce rate on the next campaigns. If you also changed your setup, a new Delivmail test confirms that authentication and blacklist checks are clean.