Blazalek.com

5.1.1SMTP 5.1.1: The recipient mailbox does not exist

5.1.1 identifies a nonexistent recipient mailbox. Stop sends to this unchanged address, verify a replacement through a trusted source, and keep the result scoped to that recipient.

Category
Addressing
Class
Permanent failure
Retry
Do not retry unchanged
Suppression
Check the full context

TL;DR

Nonexistent recipient mailbox: do not retry unchanged; correct or retire that address.

What this code means

X.1.1 means the specified mailbox does not exist; for an Internet address, the invalid part is left of the @ sign. The standard reserves this detail for permanent failures, and 5.1.1 is its class-5 form.

Provider examples

Interia example
550 5.1.1 Account not found
Rackspace example
550 5.1.1 <${user@example.com}>: Email address could not be found, or was misspelled (G8)
Gmail example
550 5.1.1 The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos or unnecessary spaces. Learn more at https://support.google.com/mail/?p=NoSuchUser - gsmtp
Gmail example
550 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. For more information, go to Fix bounced or rejected emails. - gsmtp
Yahoo / AOL example
Remote host said: 554 delivery error: dd This user doesn't have a yahoo.com account (testing123@yahoo.com) [-5] - mta123.mail.mud.yahoo.com
barracuda example
smtp;550 cuda_nsu 5.1.1 <email@example.com>... User unknown
comcast example
smtp;550 5.1.1 Not our Customer
comcast example
smtp;550 5.1.1 <example@comcast.net> recipient mailbox unallocated
comcast example
smtp;552 5.1.1 <example@comcast.net> recipient rejected - extended quota violation
Gmail example
<sanjit@greytip.com>: host aspmx.l.google.com[142.250.27.27] said: 550-5.1.1 The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1 https://support.google.com/mail/?p=NoSuchUser v11-20020a170906564b00b009fd6f428f93si881612ejr.222 - gsmtp (in reply to RCPT TO command)
iCloud example
550 5.1.1 <example@icloud.com>: user does not exist
proofpoint example
smtp;550 5.1.1 <email@example>: Recipient address rejected: User unknown
proofpoint example
smtp;550 5.1.1 <email@example.com>: Recipient address rejected: undeliverable address: host example.com[x.xx.xx.xx] said: 550 5.1.1 <email@example.com>: Recipient address rejected: user unknown
proofpoint example
smtp;550 5.1.1 - This is not a valid email address. Please verify that you have the correct email address for your recipient.

Technical meaning

The receiving system rejected the destination mailbox as nonexistent. This is an address-level condition, not a statement about every mailbox at the domain.

Delivery status

Class 5 makes the current request permanent. An unchanged retry to the same nonexistent mailbox is not expected to succeed.

Class
Permanent failure
Retry
Do not retry unchanged
Suppression
Check the full context

Retry decision

Stop automatic and manual retries to the unchanged address. Use a corrected address only when independently verified.

Suppression decision

An exact, confirmed 5.1.1 can support address-specific list hygiene under local policy. Do not suppress the entire domain or infer that unrelated recipients are invalid.

Common causes

  • The local part names a mailbox that does not exist at the destination.

Diagnostic steps

  1. Confirm the exact code, address, response text, and transaction time before correcting or retiring the address.

Actions by owner

Sender

  • Stop delivery attempts to that unchanged address and request a corrected address through a trusted channel.

Sender administrator

  • Record the address-specific outcome and apply the organization’s hygiene policy without expanding it to the whole domain.

Sources

These sources define what this enhanced status code means, mainly through the IANA registry and related RFCs. When provider examples appear on the page, they come from that provider's published documentation. Follow the links to read the original wording in context.

Last verified:

Found an error or inaccuracy? Report a correction.

Point out the part of this page that should be checked. Every report is reviewed manually.

Type of problem

Describe the issue and, if useful, suggest corrected wording.

For a factual report, include a public source when possible.

You can submit anonymously. A reply is not guaranteed.

Do not paste full bounce messages, headers, email addresses, Message-IDs, tokens, or other personal data. Redact evidence before sending.

Sending a correction shares the information you enter with Formspree so I can review and improve this page. Read the privacy notice.

Guide

Incidents

Wojtek Blazalek

Email deliverability expert

Stuck on this error code? I help teams identify rejection causes and fix authentication and reputation, so email reaches the inbox.

Hands-on deliverability work for teams that send at scale.