The 550 No Such User Error and How to Fix It

A 550 no such user error means the receiving mail server accepted the connection, looked for the mailbox you addressed, and could not find it, so it rejected the message permanently. The fix depends on which side of the bounce you sit. If you sent the email, check the address for typos and confirm it with the recipient through another channel. If you own the domain that rejected it, confirm the mailbox actually exists, that your MX records point at the mail service that hosts it, and that a recent migration or catch-all change has not orphaned the address. This guide walks through both sides, step by step.

What a 550 no such user bounce actually means

When one mail server hands a message to another, the receiving server replies with a numeric code. Codes starting with 5 are permanent failures: the server is saying “do not retry, this will never work as sent”. A 550 rejection with wording like “no such user”, “user unknown” or “mailbox unavailable” means the server that handles mail for that domain checked its list of mailboxes and found no match for the address on the envelope. Many servers also attach the enhanced status code 5.1.1, which is the standard code for a bad destination mailbox address.

The important part is who rejected it. The bounce comes from the server responsible for the recipient’s domain, not from your own provider. Your email went out fine, travelled across the internet fine, and was turned away at the front door because nobody of that name lives there. That single fact rules out most of the things people waste time checking, such as their own password, their own spam settings or their own connection.

The common causes in 2026

Almost every genuine 550 no such user bounce traces back to one of five things:

1. A typo in the address. Still the number one cause by a distance. One transposed letter, a missing dot, or “gamil” instead of “gmail” and the receiving server quite correctly reports that no such mailbox exists.
2. A deleted mailbox. The person left the company and IT removed their account, or a business tidied up old addresses. Anyone still emailing the old address gets the bounce.
3. Stale autocomplete. Your mail app remembers addresses you have used before. If a contact changed their address, autocomplete happily keeps offering the dead one, so you keep bouncing without ever mistyping anything.
4. MX records pointing at the wrong place. MX records are the DNS entries that tell the world which server receives mail for a domain. After a migration, say from mailboxes on a web hosting account to Google Workspace or Microsoft 365, mail can arrive at a server that no longer holds the mailboxes. That server answers honestly: no such user here.
5. A catch-all that was switched off. A catch-all accepts mail for any address at the domain, even ones that were never created. Businesses often disable it because it hoovers up spam. The day it goes off, every informal or misspelt address that used to work quietly starts bouncing.

There is a sixth cause worth knowing if your website and email sit on the same hosting account: some servers can be configured to believe they handle mail for a domain locally even when the real mailboxes live elsewhere. Mail generated on that server, typically from your website contact form, never leaves the building and bounces with a no such user message while everyone else’s email arrives fine. If your contact form notifications bounce but normal email works, ask your host to check whether the domain is set to local or remote mail delivery.

How to fix it if you are the sender

Work through this list in order. Most bounces are resolved at step one or two.

1. Read the bounce message. Copy the exact rejected address out of the bounce and compare it letter by letter with the address you meant to use. Do not trust your eyes on the version in the To field.
2. Delete the autocomplete entry. In Gmail, Outlook and Apple Mail you can remove a remembered address so the app stops suggesting it. Then type the address fresh.
3. Confirm the address through another channel. Phone, text, LinkedIn, or the contact page on the recipient’s website. If the person has left the company, ask who replaced them.
4. Check the domain itself. If the whole domain was mistyped, the bounce may mention a domain that does not exist or belongs to someone else. A quick visit to the website on that domain usually settles it.
5. Resend, do not wait. A 550 is permanent. The receiving server will not retry it later and neither will yours. Once you have the right address, send a fresh message.

How to fix it if you own the receiving domain

If people tell you their emails to you are bouncing, the problem is on your side of the fence. Here is the workflow we use:

1. Get the exact bounce. Ask the sender to forward the full bounce message. It names the rejected address and the server that rejected it, which tells you where to look.
2. Confirm the mailbox exists. Log in to your mail provider’s admin console (Google Workspace, Microsoft 365, or your hosting control panel) and check the address is listed as a mailbox, an alias or a group. Watch for spelling differences between what you think exists and what actually exists.
3. Check your MX records. Use any DNS lookup tool to see where your domain’s mail is routed. The records shown must match what your current mail provider says they should be. If you migrated providers and the old records are still in place, mail is being delivered to a server that no longer knows your users.
4. Fix the records and wait for DNS. Update the MX records at whoever manages your DNS, usually your domain registrar or Cloudflare. Changes can take a few hours to spread, so do not panic if bounces continue briefly after the fix.
5. Review aliases and catch-all. If the bouncing address was never a real mailbox, decide whether to create it, add it as an alias to an existing mailbox, or accept the bounce as correct behaviour. Think twice before enabling a catch-all: it stops the bounces but invites a lot of junk.
6. Test from outside. Send a test from a personal address on a different provider, not from inside your own domain, because internal mail can route differently.

If your email still lives on the same account as your website, it is worth reading our web hosting page before your next renewal. Separating the two is one of the simplest reliability upgrades a small business can make.

Match the symptom to the cause

What you see	Most likely cause	First thing to check
One contact bounces, everyone else gets through	Typo or stale autocomplete	The exact address quoted in the bounce
Everyone who emails one address gets a bounce	Mailbox deleted or never created	The mailbox list in your admin console
Every address at the domain bounces	MX records wrong or mail service lapsed	MX records against your provider’s documentation
Bounces started the day you changed provider	DNS not updated or mailboxes not recreated	Migration checklist, then MX records
Only your website’s own emails bounce	Server treating remote mail as local	Local versus remote delivery setting with your host
Odd or misspelt addresses used to work, now bounce	Catch-all switched off	Catch-all and alias settings

SPF, DKIM and DMARC failures are a different 550

Not every 550 rejection is about a missing mailbox. Receiving servers also use 550 replies to refuse mail that fails authentication checks: SPF, DKIM and DMARC. Those bounces read differently, with wording about the message being rejected for policy reasons, failing authentication, or the sending domain not being authorised. If your bounce talks about authentication or policy rather than an unknown user, the recipient’s mailbox is fine and the problem is your domain’s sending records. That is a separate repair job on your own DNS, and worth doing properly, because weak authentication also drags legitimate mail into spam folders. The fix for that has nothing to do with anything in this article, which is exactly why reading the bounce wording carefully matters.

What we said in 2014, and what has changed

This article first appeared on Luckywebs in November 2014, back when the site was a WordPress training business and most small firms ran their email on the same shared hosting account as their website. The original advice was to open your host’s live chat, ask them to “run a Fix Ownership on the server level”, then create an A record called webmail pointing at your hosting IP, and give it four hours. It also recommended a specific budget host and its chat support.

More than a decade on, we would not give that advice. The fix ownership step was a workaround for a permissions quirk on one shared hosting platform of the era, not a general cure. The webmail A record only ever affected loading webmail in a browser: mail routing is decided by MX records, so adding it was never the part that mattered. Google Apps, which the original bounce message referenced, has been Google Workspace since 2020. And the biggest change of all is structural: most businesses no longer host mailboxes on their web server at all, which means the modern causes are migrations, DNS and admin console housekeeping rather than server file permissions. The bounce message itself, though, means exactly what it meant in 2014. Some things in email never change.

Frequently asked questions

Will the email be delivered once the problem is fixed?

No. A 550 code is a permanent rejection, so no server will retry the message. Once the address is corrected or the mailbox restored, the sender has to send the email again from scratch.

The address definitely exists, so why am I getting 550 no such user?

Because the server that rejected the message does not hold that mailbox. Usually the domain’s MX records point at an old or wrong server, or the mail was generated on a web server that wrongly believes it handles the domain’s mail locally. The mailbox exists somewhere, just not where the message was delivered.

Is a full mailbox the same problem?

No. A full mailbox produces a different bounce, typically mentioning quota or storage. No such user specifically means the address was not found at all, so freeing up space will not help either side.

Should I turn on a catch-all address to stop the bounces?

It works, but treat it as a trade. A catch-all rescues mail sent to misspelt or informal addresses, and it also accepts spam sent to guessed addresses at your domain. For most small businesses a few well-chosen aliases beat a catch-all.

Can changing my domain or email provider cause these bounces?

Yes, and it is one of the most common triggers. If mailboxes are not recreated at the new provider, or MX records still point at the old one, mail bounces even though nothing looks wrong from inside. If you are still picking a domain, our guide on how to choose your domain name will save you some of this pain later.

Which tools help me check DNS and MX records?

Any reputable DNS lookup tool will show your MX records in seconds, and your mail provider’s documentation tells you what they should say. If you like having a proper toolkit for this sort of housekeeping, our SEO tools hub compares the suites we use day to day, and our best free SEO tools guide covers the free end of the market.

Get your email and your enquiries flowing again

Bounced email costs small businesses real enquiries, and it usually gets fixed in an afternoon once someone reads the bounce properly. Luckywebs is a London based SEO and web agency, rated 4.7 stars from 60 Google reviews, and untangling this sort of plumbing sits naturally alongside the website, SEO and Google Ads work we do. If you would rather sort the wider picture yourself first, start with our DIY SEO guide and our walkthrough of Google Business Profile optimisation, both of which assume working email as step zero.

Book a Free Consultation