The 550 5.1.1 error means the recipient’s email address is invalid, inactive, or has been deleted — also known as “user unknown,” “mailbox does not exist,” or “invalid recipient.”
To fix it, verify the email address for typos, clear your auto-complete cache, and manually retype the address before sending again.
Ignoring this error damages your email deliverability. Every bounce signals to email providers that you’re sending to bad addresses, which tanks your sender reputation and pushes future emails toward spam folders. If you’re seeing 550 5.1.1 repeatedly across a campaign, your list needs immediate attention.
Quick Skim — 550 5.1.1 Error Overview
Before troubleshooting, understand what you’re dealing with. The 550 5.1.1 error is a permanent failure (the “5” prefix confirms it won’t resolve on retry).
| Attribute | Details |
| Error code | 550 5.1.1 |
| Category | Addressing / mailbox state error |
| Meaning | Destination mailbox does not exist |
| Severity | Permanent (hard bounce) |
| Common causes | Typos, deleted accounts, stale CRM data, removed aliases |
| Fix approach | Verify address → suppress or update → prevent future bounces |
What does 550 5.1.1 mean?
The 550 5.1.1 error indicates the destination mailbox address does not exist on the receiving mail server. Email providers also describe this as “account does not exist,” “user unknown,” or “no such user” — the phrasing varies, but the meaning stays consistent.
SMTP code breakdown
SMTP error codes use a three-digit structure plus an enhanced code. Breaking down 550 5.1.1:
| Component | Value | Meaning |
| Basic code | 550 | Permanent failure — message will not be accepted |
| Enhanced class | 5 | Permanent condition (won’t resolve with retry) |
| Enhanced subject | 1 | Addressing problem |
| Enhanced detail | 1 | Mailbox does not exist |
The 5xx class signals a hard bounce, meaning something must change before delivery can succeed. Unlike 4xx errors (temporary deferrals that resolve with retries), 550 5.1.1 requires action from you.
Provider-specific variations
Different email providers phrase the same error differently:
| Provider | Error Message |
| Gmail | 550 5.1.1 The email account that you tried to reach does not exist (gsmtp) |
| Microsoft 365 | 550 5.1.1 RESOLVER.ADR.RecipNotFound; not found |
| Yahoo | 550 5.1.1 User unknown |
| Generic SMTP | 550 5.1.1 Mailbox does not exist |
The gsmtp suffix on Gmail bounces indicates the response came from Gmail’s SMTP edge servers.
Vs similar codes
Confusion often arises between 550 5.1.1 and related error codes. Each targets a different problem:
| Code | Meaning | Key Difference |
| 550 5.1.1 | Mailbox does not exist | Address itself is invalid |
| 550 5.1.2 | Bad destination domain | Domain part (after @) is invalid or not mail-capable |
| 550 5.1.3 | Invalid address syntax | Address format is malformed (missing @, illegal characters) |
| 550 5.2.1 | Mailbox disabled | Address exists but account is suspended/inactive |
If you’re seeing 550 5.1.2, the domain doesn’t exist or has no MX records. With 550 5.1.3, the address format itself is broken. The 550 5.1.1 error specifically means the mailbox portion (before the @) doesn’t exist on an otherwise valid domain.
Why does this error occur?
The 550 5.1.1 error stems from addressing problems — either the recipient address is wrong or the account no longer exists. Understanding the root cause determines your fix.
Typos and misspellings
Simple typos cause most 550 5.1.1 errors. A missing letter, transposed characters, or incorrect domain spelling (gmail.con instead of gmail.com) triggers an instant bounce. These errors often originate from:
- Manual data entry in forms
- Copied addresses with hidden characters
- Auto-complete suggesting outdated addresses
- Dictated email addresses with phonetic confusion
Stale CRM data
Old contact records accumulate invalid addresses over time. People change jobs (and lose their work email), companies merge or rebrand domains, and personal accounts get abandoned.
If your CRM hasn’t been cleaned recently, you’re likely sending to addresses that existed months or years ago but don’t anymore.
Deleted or deprovisioned accounts
When someone leaves an organization, IT typically deletes or disables their mailbox. The domain still exists and accepts mail — but that specific address is gone. External senders have no way to know this happened until they receive a bounce.
Removed aliases
Many email systems use aliases (alternate addresses pointing to a primary mailbox). When administrators remove an alias, mail sent to that address starts bouncing. The original mailbox still works; only the alias path is broken.
Forwarding rule failures
Some bounces that appear as 550 5.1.1 actually originate from misconfigured forwarding. If the recipient set up a forwarding rule to an invalid address, the bounce occurs at the forwarding destination — but gets reported back to you as a 550 5.1.1.
Invalid MX records
For domain administrators: if your domain’s MX records point to non-existent or misconfigured mail servers, senders receive 550 5.1.1 even when the mailbox exists. The sending server can’t find a valid path to deliver the message.
How do you fix 550 5.1.1?
Fixing 550 5.1.1 requires confirming whether the address is wrong or the account is genuinely gone. Start with verification, then either correct or suppress.
Verify the address
Copy the exact email address from your bounce notification (don’t retype it — you might introduce new errors). Compare character-by-character against your source record:
- Watch for hidden trailing punctuation (often copied from spreadsheets)
- Verify the domain spelling (gmail.com vs gmail.con or gmial.com)
- Check for transposed letters (john.smtih vs john.smith)
- Look for missing characters (johnsmith vs john.smith)
If you spot a typo, correct it in your database or CRM. For verification at scale, use an email validation API to catch invalid addresses before they bounce.
Clear auto-complete
Email clients cache recipient addresses for auto-complete suggestions. If you’ve sent to a wrong address before, your client may keep suggesting it. Remove the incorrect entry:
- Gmail: Start typing the address → hover over the suggestion → click “X” to remove
- Outlook: Start typing → use arrow keys to highlight → press Delete
- Apple Mail: Window → Previous Recipients → find and remove
After clearing, manually type the correct address.
Contact the recipient
When you’re confident the address is correct but still getting bounces, the account may have been deleted or changed. Reach out through an alternate channel:
- Phone call
- LinkedIn message
- Secondary email address
- Colleague at the same organization
Ask whether their email address changed or if a new contact address is available.
Check MX records
If you’re the administrator for the recipient domain and all addresses are bouncing, verify your MX records are correctly configured. Use a DNS lookup tool to confirm:
- MX records exist and point to valid mail servers
- SPF records don’t conflict with your mail routing
- Mail servers are reachable and accepting SMTP connections
For senders: you can’t fix the recipient’s MX records, but confirming they’re broken helps explain persistent bounces to an otherwise valid-looking domain.
Check forwarding rules
If you manage the recipient mailbox, review any forwarding rules. A rule forwarding mail to a deleted external address causes 550 5.1.1 bounces that appear to originate from the primary address. Either update the forwarding destination or remove the rule.
Provider-specific fixes
Each major provider handles 550 5.1.1 slightly differently.
Gmail (gsmtp)
Gmail’s 550 5.1.1 gsmtp bounce confirms the account doesn’t exist in Google’s systems. If you’re certain the address is correct, the account was likely deleted. Suppress the address and find an alternate contact method.
Microsoft 365
Microsoft’s RESOLVER.ADR.RecipNotFound error indicates directory-based rejection. For tenant administrators: verify the mailbox exists in the admin center, check that proxy addresses are correctly configured, and confirm the accepted domain is properly synced.
Yahoo
Yahoo’s “User unknown” bounce works identically to other providers. Verify the address, suppress if invalid, or contact the recipient through other means.
Suppress or update
If you’ve confirmed the address is invalid and can’t obtain a corrected version:
- Mark the address as a hard bounce in your sending platform
- Add it to your suppression list
- Remove it from active campaigns
Never keep sending to addresses that return 550 5.1.1. Continued bouncing damages your sender reputation.
What should you do after fixing?
Resolving a single 550 5.1.1 bounce is just the start. Prevent future damage with these follow-up steps.
Confirm delivery
After correcting an address, send a test message and verify it arrives. Check your sending logs for a 250 response code, which confirms acceptance by the receiving server. Run an email deliverability test to confirm your overall sending health hasn’t degraded.
Update your suppression list
Add confirmed invalid addresses to your email suppression list. Most email platforms automatically suppress hard bounces, but verify the addresses are blocked from future sends. This protects your reputation from accidental re-sends.
Review your bounce rate
Check your overall bounce rate after the incident. Major email providers flag senders with bounce rates above 2-3%. If 550 5.1.1 errors pushed you over that threshold, pause campaigns and clean your list before resuming.
Audit your list source
Ask where the bad addresses came from:
- Manual entry errors?
- Old database import?
- Web form with no validation?
- Purchased list (almost always problematic)?
Fixing the source prevents future invalid addresses from entering your system.
How do you prevent this error?
Prevention costs far less than remediation. Build validation into your workflow to stop 550 5.1.1 errors before they happen.
Validate at point of entry
Catch typos before they reach your database. Implement real-time validation on signup forms, checkout flows, and CRM data entry. An email validation API can verify syntax, check domain validity, and flag disposable or non-existent addresses instantly.
Clean your list regularly
Old lists accumulate dead addresses. Schedule quarterly (or monthly, for high-volume senders) email list hygiene reviews:
- Remove addresses that bounced
- Re-verify addresses that haven’t engaged in 6+ months
- Check for known spam traps (often recycled from abandoned accounts)
Monitor engagement
Unengaged recipients often correlate with invalid addresses. If someone hasn’t opened or clicked in 6-12 months, their account may be abandoned (or heading that way). Segment low-engagement contacts and verify before continuing to send.
Use double opt-in
Double opt-in requires new subscribers to click a confirmation link before joining your list. This:
- Verifies the address actually works
- Confirms the owner intentionally subscribed
- Catches typos immediately (confirmation email bounces)
The slight friction reduces signups but dramatically improves list quality.
Watch your bounce reports
Don’t wait for problems to compound. Review bounce reports weekly and investigate any spike in 550 5.1.1 errors. A sudden increase often indicates a data import issue, form validation failure, or domain-wide problem at a recipient organization.
Still stuck after trying the fix?
Some email errors are easy to clear. Others point to deeper deliverability issues involving authentication, sender reputation, blacklisting, routing, or mailbox provider policy. If you would rather have an expert review it, speak with an email delieverability consultant for free and we can help diagnose the issue and fix it on your behalf.
We look beyond the error message itself to find what is actually breaking delivery, trust, or inbox placement.
From SPF, DKIM, and DMARC to blacklist cleanup, DNS alignment, and sending setup, we can guide or implement the fix.
We assess whether the error is part of a bigger pattern hurting opens, replies, and overall campaign performance.
Talk to a real deliverability expert, get honest guidance, and see the next best step without pressure or upsells.
When should you book a consultation? If the error keeps coming back, affects multiple mailboxes or domains, started after an ESP or DNS change, or is tied to spam placement, low inboxing, high bounce rates, or authentication failures, it is usually faster to get an expert involved early.
Frequently asked questions
Here are some commonly asked questions about this error:
The 550 5.1.1 error is permanent (a hard bounce). The “5” prefix in both the basic code and enhanced code confirms the receiving server will not accept this message as-is, and retrying won’t help. You must either correct the address or suppress it from future sends.
Retrying the same message to the same address won’t work — the mailbox doesn’t exist, so the result stays the same. However, if you’ve corrected a typo or obtained a new address for the recipient, sending to the corrected address should succeed (assuming that address is valid).
Yes. Hard bounces signal to email providers that you’re sending to invalid addresses, which suggests poor list quality. High bounce rates (above 2-3%) trigger reputation penalties, reduced delivery rates, and potential blacklisting. Suppress bouncing addresses immediately and clean your list regularly.
The most common reason is account deletion — the recipient left their job, changed email providers, or abandoned the account. Domain changes (company mergers, rebranding) and removed aliases also cause previously valid addresses to start bouncing.
The 550 5.1.1 error originates from the recipient’s mail server, so technically the “problem” is always on the recipient side (the mailbox doesn’t exist). However, the cause may be your data — a typo means your record is wrong, even though the bounce comes from their server. Verify your address data first before assuming the recipient’s account is gone.
