Opens in a new tab

SMTP 5.1.1: bad destination mailbox address — the fix

5.1.1 means the mailbox does not exist: the part of the address before the @ is wrong, or the account was closed. It is the most common bounce there is, and it is permanent — sending again to the same address will fail again.

Code5.1.1
MeaningBad destination mailbox address
KindPermanent failure — the sender gives up
Sent in reply toRCPT, with 550
What the sender doesReturns the message to the sender
Defined inRFC 3463

Paste your bounce

Paste the line with the code — or the whole bounce: we explain each code in it, say whether the sender will try again, and link the service’s own page where it has one. It is read in your browser; nothing is sent.

What causes it

  • A typo, or a space, in the address.
  • The person left, or the mailbox was deleted.
  • At Microsoft 365: an Outlook address cache that still holds an old address, or MX records pointing at an old server.

What to do

  • Check the address with the recipient another way.
  • Remove addresses that return 5.1.1 from mailing lists: repeated sends to missing mailboxes hurt your reputation.

What each provider means by it

WhoWhat they say
Gmail550 5.1.1 The email account that you tried to reach does not exist. Please double-check the recipient’s email address for typos or unnecessary spaces.
Microsoft 3655.1.1 Bad destination mailbox address — a mistyped address, a mailbox that does not exist, a stale Outlook cache, or MX records pointing to an old server.
Outlook.comFor @outlook.com and @hotmail.com addresses that do not exist, answers 550 5.5.0 “Requested action not taken: mailbox unavailable” instead.
YahooPublishes no enhanced codes; a recipient that does not exist is permanent — do not retry.

Related: 550, 5.5.0, 5.2.1, 5.1.10.

Questions

The address is right, but I still get 5.1.1 — why?

Either the mailbox really was closed, or, at Microsoft 365, the recipient’s own organisation has a routing problem — stale MX records or a missing mailbox after a migration. Only the recipient’s administrator can fix that.

Sources

Checked on 27 September 2026 against these official sources:

See every bounce before your customers do

Add your domain and send us a test message: we show what a receiving server saw — authentication, reverse DNS, blocklists, TLS — and monitor the servers you send from for blocklistings every day. Free for your first domain.

Create a free account