Critical ErrorSMTP Error · Permanent (5.x.x)
550 5.1.1

Recipient address does not exist

A 550 5.1.1 bounce means the receiving server accepted your connection but rejected the recipient — the mailbox you tried to reach does not exist on that domain.

Updated June 13, 2026

SMTP Exchange / Mail Log
> MAIL FROM:<you@yourdomain.com>> RCPT TO:<recipient@example.com>✕ 550 5.1.1 Recipient address does not exist
All guides

Is your domain affected?

Run a free check — we'll show you exactly what's misconfigured.

550 5.1.1 is a permanent SMTP reply meaning recipient address does not exist. The recipient's mail server is telling you "no such user here." The local part (the bit before the @) does not match any mailbox, alias, or distribution list on that domain.

What 550 5.1.1 means

The recipient's mail server is telling you "no such user here." The local part (the bit before the @) does not match any mailbox, alias, or distribution list on that domain.

⚠️
This is a 5.x.x permanent failure — the message will keep bouncing until you fix the cause. Retrying the same message unchanged won't help.

Common causes

📨
#1

The address is mistyped or has a typo

Most common

A single wrong character (jonh@ vs john@) produces this bounce. The most common cause by far.

🔁
#2

The mailbox was deleted or the person left

Common

Employees leave and mailboxes get removed; old addresses on your list then bounce 5.1.1.

⚙️
#3

You're mailing a stale or purchased list

Common

High 5.1.1 rates across many recipients signal an old or low-quality list — which also hurts your sender reputation.

How to fix 550 5.1.1

  1. 1

    Verify the exact address

    Confirm the spelling with the recipient or check it against a known-good source. For a single contact, this is usually all it takes.

  2. 2

    Remove bouncing addresses from your list

    Permanently suppress any address that returns 5.1.1 — continuing to mail it damages your reputation and can land you on a blacklist.

  3. 3

    Use list validation before big sends

    For marketing lists, run email verification to catch non-existent mailboxes before they bounce and drag down your deliverability.

Confirm your domain is set up correctly

Most delivery failures — permanent or temporary — trace back to authentication or reputation. Run a free EmailHealth check to confirm SPF, DKIM, DMARC, blacklist status, and TLS are all healthy for your sending domain. If you send in volume, free daily monitoring will alert you before a small issue becomes a flood of bounces.

Stop this error from coming back

Most delivery problems start when a DNS record changes, a key is removed or a domain lands on a blocklist. EmailHealth checks your sending domains every day and sends one alert, by email, Slack or webhook, with the exact fix.

1 domain free. Sending from many domains (cold email, agencies, MSPs)? Early access covers 10.

Frequently asked questions

Check your domain for free

SPF, DKIM, DMARC, MX, blocklists and TLS in about 2 seconds. No account needed.

Run the check