SMTP error 5.2.1 Mailbox disabled, not accepting messages

What SMTP error 5.2.1 means

The mailbox is real and is not taking delivery. Somebody has put it into a state where it accepts no mail — suspended, disabled, locked during a move, or blocked by a policy on the account. Unlike an unknown recipient the address is recognised perfectly well, which is why the wording mentions the mailbox being disabled or unavailable. IANA registers no basic reply code for it, so the three-digit number in front depends on the platform.

Mailbox status
Sent by The receiving mail platform, where the mailbox exists but has been switched off
Occasional

What SMTP error 5.2.1 Mailbox disabled, not accepting messages actually means

RFC 3463 explicitly allows this condition to be reported either way, and the class digit is the important part. As 5.2.1 the receiving system is saying the mailbox will not be re-enabled, or not soon enough to matter, and the message is returned. As 4.2.1 it is saying the mailbox is off temporarily, so the sending server keeps the message queued and retries, typically for a day or two. That one digit is the difference between telling a customer their email bounced and telling them it is still on its way. It also separates this from a full mailbox: nothing here is about space, and clearing messages out would change nothing.

The mailbox exists, but is not accepting messages. This may be a permanent error if the mailbox will never be re-enabled or a transient error if the mailbox is only temporarily disabled.
— RFC 3463

How 5.2.1 appears in a bounce

The leading 5 is the server's verdict rather than part of the code's identity: it marks this as a permanent failure, which means the sending server has given up and returned the message. The same condition reported as 4.2.1 is the other verdict on the identical problem, so a log showing that form has not produced a bounce yet.

RFC 3463 is explicit about which verdicts this code can carry: “This may be a permanent error if the mailbox will never be re-enabled or a transient error if the message is being rejected temporarily.”

What causes SMTP error 5.2.1 on a business phone system

A hosted mailbox suspended for non-paymentSmaller providers and legacy POP or IMAP packages suspend individual mailboxes when an invoice goes unpaid rather than closing the account. The address survives, delivery stops, and a customer usually reports it before the provider does.
An account deliberately blocked during an incidentAfter a compromise or a suspected one, blocking sign-in and stopping delivery buys time to investigate. The right move, but if nobody tells the wider business, senders keep writing and collecting bounces.
A mailbox locked mid-migrationAt the final stage of a move between platforms or tenants, the source mailbox is put beyond use so nothing new lands in the copy being abandoned. Where the cutover overruns or MX records lag, senders reach the old system.
A disabled or disconnected mailbox on an on-premise Exchange serverDisabling a mailbox in Exchange severs it from its account and leaves it disconnected in the database awaiting purge. In a hybrid setup that still routes some addresses on-premise, mail arrives at a mailbox accepting nothing.
A restriction on who the mailbox will accept mail fromMailboxes can be set to accept mail only from inside the organisation or from a named list, common on internal-only addresses. Some platforms surface that refusal here, though a policy rejection is more usually a 5.7.x code.

How to fix SMTP error 5.2.1

Establish whether it is a 4 or a 5Read the class digit before anything else. A 4 means the message is still queued and being retried, so sorting the mailbox out within the retry window may be all that is needed. A 5 means it has already been returned.
Check the account state in the admin centreFor a mailbox on your own tenant, look at whether sign-in is blocked, whether the licence is still assigned and whether the mailbox is in a hold or migration state. Get-Mailbox reports the type and whether it is genuinely active.
Confirm the provider has not suspended the serviceWhere the mailbox sits with a hosting provider, check billing status and any suspension notices. Suspension for an unpaid invoice is one of the few causes no amount of configuration work will resolve.
Redirect the address while the mailbox is out of actionIf the block will stand for any length of time, point the address at a shared mailbox the team can watch. Enquiries keep flowing rather than accumulating as bounces on the sender's side.
Recheck the migration state if a cutover is under wayConfirm the mailbox has completed its move, that MX records point at the destination and that no connector still routes to the source. Delivery to a locked source mailbox mid-cutover is the most common version in practice.

Fixing the underlying problem

This page explains the code. These guides walk through the fix in detail.

Questions about SMTP error 5.2.1

Is this the same as the mailbox being full?

No, and the difference decides what you do next. A full mailbox is a capacity problem the recipient can solve by deleting messages or being given more space. This is a switch turned off deliberately, so freeing space achieves nothing and somebody with administrative access has to turn it back on.

Will messages sent while the mailbox was disabled arrive once it is back?

Only those still sitting in a sending queue, which means only the ones refused with a 4 rather than a 5. Anything permanently refused was returned at the time. When you re-enable a mailbox after any real length of time, tell people they may need to resend.

Our mailbox was disabled after a suspected compromise. What should we tell people?

Tell key contacts directly using an alternative address, and put a redirect on the address so nothing is lost while the investigation runs. Do not re-enable delivery before the account is confirmed clean, because a compromised mailbox that is still receiving is still useful to an attacker.

Related SMTP status codes

Source. SMTP error 5.2.1 Mailbox disabled, not accepting messages is defined in RFC 3463 and registered in the IANA SMTP Enhanced Status Codes registry. The causes and fixes above are drawn from our own experience supporting UK business email systems.

All Email delivery & SMTP codes