5.2.1: the mailbox exists but is disabled

What the bounce means

The enhanced status code 5.2.1 means the receiving server recognized the recipient address but refused delivery because the mailbox behind it is disabled or not accepting mail. It usually appears as 550 5.2.1 with wording like “mailbox disabled” or “account inactive,” though the reply code and text vary by server; the enhanced code is the reliable part.

Nothing about your sending setup is in question. SPF, DKIM, DMARC, and your reputation never entered into it: the server simply will not put mail into that mailbox right now. The useful distinction from other bad-address codes is that this mailbox exists. Someone created it, and the server still knows about it.

Why a mailbox gets disabled

• The account was suspended. An employer disables a departing employee's account before eventually deleting it, or a school deactivates alumni mailboxes at the end of a grace period. 5.2.1 is often the first stage of an address on its way to 5.1.1.
• The provider froze it. Mailbox providers disable accounts for policy violations, compromise cleanup, or unpaid hosting bills. The owner may not even know until they try to log in.
• The inbox was abandoned. Some providers deactivate mailboxes that have not been signed into for a long time. Seasonal addresses, old personal accounts, and forgotten signups age into this state.

How to handle it

The honest answer is that this one is sometimes temporary from the recipient's side: the owner can reactivate the account, settle the bill, or clear the hold, and the same address will take mail again. But none of that is visible or actionable from where you sit, and the server is returning a permanent code today. So treat it as permanent for sending purposes:

• Suppress the address now. Do not retry-loop it and do not leave it in an active segment. Each new send is another hard bounce on your record, and receivers notice senders who keep mailing addresses that hard-bounce.
• Restore it only on a positive signal. If the person re-subscribes, replies from that address, or completes a confirmation email, the mailbox is back; lift the suppression then. That signal-driven path is the safe way to benefit from a reactivated account without gambling sends on it.
• For contacts that matter, go out of band. A key customer whose address returns 5.2.1 has probably changed jobs or lost the account. Reach them another way and capture a current address.

Frequently asked

What does a 5.2.1 bounce mean?

The receiving server recognized the recipient address, but the mailbox behind it is disabled or not accepting mail: a suspended account, a frozen mailbox, or an inbox the provider has deactivated. The address is the problem, not your sending setup.

Will a 5.2.1 address start working again?

It can. Disabled is not deleted: if the account owner reactivates, pays an overdue bill, or clears whatever hold the provider placed, the same address can accept mail again. But you cannot see or influence any of that from the sending side, so treat the address as undeliverable until you learn otherwise.

How is 5.2.1 different from 5.1.1?

5.1.1 means no mailbox by that name exists: it was never created, or it was removed. 5.2.1 means the mailbox is there but switched off. The practical handling is the same, suppress and stop sending, but a 5.2.1 address has a real chance of coming back where a 5.1.1 address usually does not.

Should I keep sending in case the account comes back?

No. Every send to a disabled mailbox is a fresh permanent bounce, and a sender who keeps mailing hard-bouncing addresses looks careless to receivers. Suppress the address and only restore it on a positive signal, such as the person re-subscribing or replying from that address.