An SMTP error has three parts: a three-digit reply code (RFC 5321), an optional enhanced status code in the form class.subject.detail (RFC 3463), and free text from the provider. The first digit tells you what to do: 4xx means try again later on a schedule, 5xx means stop and fix the cause before sending to that recipient again. The provider text tells you which cause to fix.
This guide reads codes from the cold sender's side: you send reviewed B2B email through your own mailbox or SMTP server, a campaign stalls, and you need to know whether to wait, slow down, fix DNS or remove an address. Each code links to a dedicated fix page where one exists.
How to read a bounce line
Take this fictional bounce, received when a mailbox at northfield-consulting.example wrote to a Gmail address:
550-5.7.26 This email has been blocked because the sender is unauthenticated.
550-5.7.26 Gmail requires all senders to authenticate with either SPF or DKIM.
550 5.7.26 Authentication results: DKIM = did not pass SPF [northfield-consulting.example] with ip: [192.0.2.25] = did not pass. ... - gsmtp
| Part | Value | What it tells you |
|---|---|---|
| Basic reply code | 550 | Permanent failure. RFC 5321 defines 550 as "Requested action not taken: mailbox unavailable", which servers also use for policy rejections. |
| Hyphen after the code | 550- | A multi-line reply. Every line but the last uses a hyphen; the last uses a space. It is the same error, not three. |
| Enhanced code class | 5 | Permanent failure (RFC 3463: 2 success, 4 persistent transient failure, 5 permanent failure). |
| Enhanced code subject | 7 | Security or policy status. |
| Enhanced code detail | 26 | IANA registers X.7.26 as "Multiple authentication checks failed". |
| Provider text | "sender is unauthenticated ... SPF ... did not pass" | The actual cause: neither SPF nor DKIM passed for this message. |
| Trailer | gsmtp | Gmail's own servers wrote this reply, not a gateway in between. |
The RFC 3463 subjects are worth memorising because they narrow the cause before you read a word of text:
| Subject | RFC 3463 name | Typical cold email cause |
|---|---|---|
| X.0.x | Other or undefined status | Vague provider rejection; read the text |
| X.1.x | Addressing status | Bad address, unknown domain |
| X.2.x | Mailbox status | Mailbox full, disabled, receiving too fast |
| X.3.x | Mail system status | Message too big, system problem |
| X.4.x | Network and routing status | Routing failure, congestion, timeouts |
| X.5.x | Mail delivery protocol status | Protocol errors, too many recipients |
| X.6.x | Message content or media status | Content conversion problems |
| X.7.x | Security or policy status | Authentication, reputation, blocks, quotas |
One warning before the table. Providers reuse enhanced codes loosely. IANA registers X.7.27 as "Sender address has null MX" and X.7.30 as "REQUIRETLS support required", yet Gmail uses 5.7.27 for an SPF failure and 5.7.30 for a DKIM failure. Microsoft's 5.7.7xx and 5.7.139 codes are not in the IANA registry at all. Always read the provider text and do not rely on the registry title alone.
The codes cold senders actually see
These are the replies that turn up most in B2B campaigns sent from a company mailbox or a small SMTP server. Text in code formatting is quoted or closely abridged from the provider's published lists (Google, Microsoft, Yahoo, Mimecast); square brackets mark values that change.
Authentication failures
| Code | Provider text (abridged) | Likely cause | Decision |
|---|---|---|---|
550 5.7.26 (Gmail) | "This email has been blocked because the sender is unauthenticated" | SPF and DKIM both failed | Stop. Fix SPF or DKIM. See Gmail 550-5.7.26 unauthenticated sender |
550 5.7.26 (Gmail) | "Unauthenticated email from [domain] is not accepted due to domain's DMARC policy" | DMARC failed under p=quarantine or p=reject | Stop. Fix alignment |
421 4.7.26 / 421 4.7.27 / 421 4.7.30 (Gmail) | "rate limited because it is unauthenticated" / "SPF authentication didn't pass" / "DKIM authentication didn't pass" | One method failing, mail slowed rather than refused | Pause and fix; retries will keep being throttled |
550 5.7.40 / 421 4.7.40 (Gmail) | "the sending domain doesn't have a DMARC record" | Bulk sender with no DMARC policy | Publish DMARC (p=none is allowed) |
421 4.7.32 (Gmail) | "From: header ... isn't aligned" | From domain matches neither SPF nor DKIM domain | Fix alignment |
554 5.7.5 | "Permanent error evaluating DMARC policy" | Broken DMARC or SPF record | Stop. See 554 5.7.5 DMARC permanent error |
550 5.7.515 (Outlook.com) | "must be authenticated with SPF, DKIM, and DMARC" | High-volume sender to Outlook.com without all three | Stop and publish all three |
535 5.7.139 (Microsoft 365) | "Authentication unsuccessful, SmtpClientAuthentication is disabled for the Tenant" | Your own login to smtp.office365.com refused | Not a bounce; fix SMTP AUTH. See 535 5.7.139 SMTP AUTH fix |
Reputation and blocks
| Code | Provider text (abridged) | Likely cause | Decision |
|---|---|---|---|
550 5.7.1 (Gmail) | "This message is likely unsolicited email" | Content and sender reputation | Stop to Gmail |
421 4.7.0 (Gmail) | "suspicious due to the very low reputation of the sending IP address" or "sending domain" | Poor reputation | Slow down sharply; see 421 4.7.0 try again later |
421 4.7.0 (Gmail) | "The IP address sending this message does not have a PTR record" | Missing or mismatched reverse DNS | Fix PTR with your host |
550 5.7.708 (Microsoft 365) | "Access denied, traffic not accepted from this IP" | Your tenant's outbound IP has low reputation | Stop. See 550 5.7.708 traffic not accepted |
550 5.7.705 (Microsoft 365) | "Access denied, tenant has exceeded threshold" | Tenant sent too much spam or bulk mail | Stop all sending; admin must fix and contact support |
550 5.1.8 (Microsoft 365) | "Access denied, bad outbound sender" | Your user is on the Restricted entities list | Stop; admin unblocks after securing the account |
550 5.7.1 ... (S3150) (Outlook.com) | "part of their network is on our block list" | IP or range blocked by Outlook.com | Stop to Outlook.com; see Outlook S3150 block list |
550 SC-001 / OU-002 (Outlook.com) | "content with spam-like characteristics or IP/domain reputation" | Reputation or content | Stop; review content and reputation |
550 DY-001 (Outlook.com) | "We generally do not accept email from dynamic IP's" | Sending from a home or dynamic IP | Use a proper mail server or provider |
550 5.7.1 with a Spamhaus link | "Client host [IP] blocked using Spamhaus" | IP on a Spamhaus list | Stop; see Outlook S3150 block list for the delisting steps |
550 (Mimecast) | "Local CT IP Reputation - (reject)" | Poor IP reputation at the recipient's gateway | Stop; the recipient can permit you, or request a review |
550 (Mimecast) | "Administrative prohibition envelope blocked" | Recipient's block policy or an SPF hard fail | Stop; only the recipient or your SPF fix can clear it |
Rate and volume
| Code | Provider text (abridged) | Likely cause | Decision |
|---|---|---|---|
421 4.7.28 (Gmail) | "Gmail has detected an unusual rate of unsolicited email originating from your IP address" (or IP Netblock, DKIM domain, SPF domain, URL domain) | Too much mail, or too much unwanted mail, from one identity | Stop for at least 10 minutes, then resume slowly |
450 4.2.1 (Gmail) | "The user you are trying to contact is receiving email too quickly" | One recipient getting a flood | Retry later; do not send multiple steps close together |
550 5.4.5 (Gmail) | "Daily user sending limit exceeded" | Your own Gmail or Workspace quota | Wait up to 24 hours; see 550 5.4.5 daily sending quota |
421 RP-001 (Outlook.com) | "has exceeded the rate limit allowed" | Sending too fast for your reputation | Reduce rate; retry later |
421 RP-003 (Outlook.com) | "has exceeded the connection limit allowed" | Too many simultaneous connections | Lower concurrency |
421 4.7.0 [TSS04] (Yahoo) | Bounces commonly read "temporarily deferred due to unexpected volume or user complaints"; Yahoo documents TS* codes only as temporary deferrals | Yahoo TS-class deferral | Retry slowly; see 421 4.7.0 try again later |
451 4.7.1 (many hosts) | "Greylisted, try again after some time" | Greylisting of an unfamiliar sender | Retry normally; see 451 4.7.1 greylisted |
451 (Mimecast) | "Internal resources are temporarily unavailable" | Usually greylisting or IP reputation | Retry from the same server |
Recipient problems
| Code | Provider text (abridged) | Likely cause | Decision |
|---|---|---|---|
550 5.1.1 (Gmail) | "The email account that you tried to reach does not exist" | Address does not exist | Remove permanently |
550 5.2.1 (Gmail) | "The email account that you tried to reach is inactive" | Disabled mailbox | Remove |
553 5.1.2 (Gmail) | "We weren't able to find the recipient domain" | Domain typo or dead domain | Remove or correct |
452 4.2.2 / 552 5.2.2 (Gmail) | "The recipient's inbox is out of storage space" (552 adds "and inactive") | Full mailbox | 452 retry later; 552 remove. |
554 delivery error: dd This user doesn't have a yahoo.com account (Yahoo) | Account does not exist | Address does not exist | Remove |
Your own configuration
| Code | Provider text (abridged) | Likely cause | Decision |
|---|---|---|---|
550 5.7.1 relaying denied | Server refuses to relay for you | Not authenticated to your own SMTP server, or wrong host | Fix client settings |
421 4.7.0 (Gmail) | "TLS required for RCPT domain, closing connection" | Your server did not use TLS | Enable STARTTLS |
550 5.7.750 (Microsoft 365) | "Client blocked from sending from unregistered domain" | Sending as a domain not accepted in the tenant | Add and verify the domain |
552 5.3.4 (Gmail) | "Your message exceeded Google's message size limits" | Attachment too large | Remove attachments; cold email rarely needs them |
550 5.7.1 (Gmail, RFC 5322 variants) | Missing or duplicate From:, missing Message-ID: and similar | Malformed message headers | Fix your sending software or template |
If Microsoft 365 rejects your login with 535 5.7.139, read SMTP AUTH disabled before changing anything else.
Retry or stop: the rules
RFC 5321 section 4.2.1 sets the basic contract. A 4yz reply is a "Transient Negative Completion reply": the action did not happen, "the error condition is temporary", and "the SMTP client SHOULD try again". A 5yz reply is a "Permanent Negative Completion reply", and the client "SHOULD NOT repeat the exact request (in the same sequence)". Yahoo's guidance is blunter: "You should not retry sending an email that comes back with a 5xx error."
For a general mail server, RFC 5321 section 4.5.4.1 says the retry interval "SHOULD be at least 30 minutes" and the give-up time "generally needs to be at least 4-5 days". A cold campaign is not a general mail server, and the rules below are stricter because each retry spends reputation.
| Situation | Rule |
|---|---|
| Single 4xx for one recipient (greylisting, mailbox busy) | Let the queue retry: first retry after 5 to 30 minutes, then wider gaps. Same server, same envelope sender. |
| 4xx naming your IP, domain or "unusual rate" | Pause sends to that provider. Google says do not send for at least 10 minutes, then resume gradually. Lower the hourly cap before resuming. |
| Repeated 4xx from one provider over hours | Treat it as a warning that is about to become a 5xx. Stop that provider for the day and look at volume, complaints and authentication. |
| 5xx naming the recipient (5.1.1, 5.2.1, 5.1.2) | Remove the address. Never resend. Add it to suppression. |
| 5xx naming authentication or policy (5.7.x) | Stop all sends to that provider until the cause is fixed and a test message passes. |
| 5xx naming your account or quota (5.4.5, 5.7.705, 5.1.8) | Stop the whole sender. Nothing will go out until the limit resets or the admin acts. |
| Connection lost after DATA, no reply | Outcome unknown. Do not resend automatically; check the sent folder or server logs first, or the recipient may get it twice. |
Two consequences follow. First, the bounce rate of a campaign includes your own mistakes: a broken DKIM key produces a wave of 5.7.x bounces against perfectly good addresses, so do not purge those addresses. Second, a high rate of 5.1.1 bounces says the list is old or guessed, and providers treat that as a spam signal of its own.
Provider differences
Gmail and Google Workspace. Google publishes the most complete list, and its text is specific: it names the failing check (SPF, DKIM, DMARC, PTR, TLS) and whether the problem is the IP, the netblock, the DKIM domain or a URL in the message. Since February 2024 all senders to personal Gmail accounts must use SPF or DKIM, have valid forward and reverse DNS, use TLS and keep the spam rate reported in Postmaster Tools below 0.3%. Senders of more than 5,000 messages a day also need DMARC, alignment and one-click unsubscribe for marketing mail. A Gmail reply ending in gsmtp came from Google itself.
Microsoft 365 and Outlook.com. These are two systems. Codes in the 5.7.7xx range and 5.1.8 come from Exchange Online protecting its own outbound mail: they mean your tenant or user is restricted, not that the recipient refused you. Codes with bracketed suffixes such as (S3150), and the RP, SC, DY and OU families, come from Outlook.com's consumer filtering of mail sent to outlook.com, hotmail.com and live.com addresses. Outlook.com now also requires SPF, DKIM and DMARC from senders of more than 5,000 messages a day and rejects with 550 5.7.515.
Yahoo. Yahoo publishes categories rather than every code: 421 and 451 are temporary blocks ("Retry later"), 553 and 554 are permanent, and bracketed codes starting TS (temporary deferral) or PH (content) give the reason. Persistent TS errors are worth a Sender Support Request with the diagnostic code from your logs.
Zoho. Zoho Mail greylists unfamiliar senders and answers with 451 4.7.1 Greylisted, try again after some time. It is the most common greylisting string in search results. A properly configured server delivers on the next attempt.
Mimecast and other gateways. Many UK firms put Mimecast, Proofpoint or a similar gateway in front of Microsoft 365. Gateway text is about the recipient organisation's policy: "Envelope blocked - User Entry" means an individual blocked you, and "Administrative prohibition" means a block policy or an SPF hard fail. Mimecast says its 451 greylisting replies should be retried from one minute to 12 hours. Look at the MX record of the recipient domain: if it points at a gateway, the gateway wrote the bounce.
When 250 OK does not mean delivered
A 250 reply at the end of DATA means, in the words of RFC 5321 section 6.1, that the receiving server "is accepting responsibility for delivering or relaying the message". It does not mean inbox. After a 250:
- The provider can still file the message in spam or quarantine, and you will never get a bounce for that.
- A gateway can accept the message and pass it to the real mailbox host, which then rejects it. You receive that rejection later as a bounce message (an NDR or DSN) in your inbox, not as an SMTP reply.
- A catch-all domain accepts every address at SMTP time, so a 250 says nothing about whether the person exists.
- Your own SMTP provider's 250 only means it accepted the message from you. Delivery to the recipient happens on the next hop.
So a campaign report that counts 250 replies as "delivered" will overstate results. Count them as "accepted", then subtract bounces that arrive later, and judge placement by replies and by provider tools such as Google Postmaster Tools and Microsoft SNDS.
A quick triage routine
When a campaign stalls, work through this list in order:
- Pause the campaign. Each extra attempt against a blocking provider adds to the problem.
- Group bounces by provider and code. Twenty 5.7.26 bounces from Gmail is one problem, not twenty.
- Separate recipient errors from sender errors. X.1.x and X.2.x are usually about the address; X.7.x is usually about you.
- Read the full provider text, including any URL it gives.
- Send a test message from the same mailbox to a personal Gmail and an Outlook.com account you control, and read the
Authentication-Resultsheader. - Fix one cause at a time and retest before resuming.
- Resume at a lower volume than before and watch the next hundred sends closely.
How Map Extract helps
The bulk email sender in Map Extract sends reviewed B2B campaigns through your own SMTP accounts, so the bounce codes in this guide are exactly what you will see in its Replies and bounces view. What it does that is relevant here:
- Automatic pause on bounces. Replies and bounces are read over IMAP, and a campaign stops itself when bounces reach the threshold, 5% by default. That limits the damage from a broken DKIM key or a stale list before you have time to look.
- No blind retries of uncertain sends. If a send fails in an ambiguous way after the message data has gone, the outbox marks it Uncertain and does not resend it automatically, which avoids the duplicate-message problem in the retry table above.
- Accepted is not delivered. The outbox distinguishes queued, accepted and uncertain items, and the software states that a sent status means your mail server accepted the message, not that it reached the inbox.
- Pacing you control. Hourly, daily and monthly caps, a minimum delay, per-route ceilings and an optional warm-up ramp keep volume within what a new mailbox can sustain, which is the main defence against 421 4.7.28 and Outlook.com RP errors.
- Suppression and permission checks. Opt-outs join the suppression list, suppression is applied again before each send, and every recipient needs a recorded permission basis.
What it does not do: it does not check or fix your SPF, DKIM or DMARC records, it does not supply an SMTP service, and it does not decode every provider's bounce text for you. Set up your domain with your mail provider first, then use the campaign's bounce view and this guide together.
Key takeaways
- Read the first digit first: 4xx means retry on a schedule, 5xx means stop and fix.
- The enhanced code's middle digit narrows the cause: X.1 and X.2 are about the address, X.7 is usually about you.
- Provider text beats registry titles; Gmail and Microsoft reuse or invent enhanced codes.
- Never resend a 5xx unchanged, and never auto-resend a send whose outcome is unknown.
- 250 OK means accepted for delivery, not delivered to the inbox.
- Pause at the first sign of 4.7.x deferrals naming your IP or domain; they become 5xx blocks if ignored.
Frequently asked questions
What is the difference between a 4xx and a 5xx SMTP error?
A 4xx reply is a transient failure: the server did not take the message this time but the sender may try again later, and RFC 5321 says the client should retry. A 5xx reply is a permanent failure: the client should not repeat the same request unchanged. For cold email, a 4xx means slow down and retry on a schedule, and a 5xx means stop and fix the cause or remove the address.
What does the second number in 550 5.7.1 mean?
The 5.7.1 part is an enhanced status code defined in RFC 3463, written as class.subject.detail. The class (5) says the failure is permanent, the subject (7) says it concerns security or policy, and the detail (1) says delivery was not authorised. The three-digit 550 is the basic SMTP reply code. Providers add free text after both, and that text usually names the real cause.
Should I retry an email that bounced with a 5xx code?
Not unchanged. RFC 5321 says the client should not repeat the exact request after a permanent negative reply, and Yahoo's sender guidance says plainly that you should not retry a message that comes back with a 5xx error. Fix the cause first, such as authentication, a quota or a bad address, then send again only where the fix applies to that recipient.
Does a 250 OK mean my email reached the inbox?
No. A 250 reply after the message data means the receiving server accepted responsibility for delivering or relaying it, as RFC 5321 section 6.1 describes. The message can still be filtered into spam, quarantined, or bounced later by a gateway further down the chain. Treat 250 as accepted, not delivered, and watch for later bounce messages and replies.
How long should I keep retrying a deferred email?
RFC 5321 recommends a retry interval of at least 30 minutes and a give-up time of at least four to five days for a general mail server. A cold campaign should usually stop sooner: if a recipient domain is still deferring after a few attempts over a day, pause that domain, reduce volume and investigate rather than keep pushing.
Sources
- RFC 5321: Simple Mail Transfer Protocol
- RFC 3463: Enhanced Mail System Status Codes
- IANA: SMTP Enhanced Status Codes registry
- Google Workspace: Gmail SMTP errors and codes
- Google: Email sender guidelines
- Microsoft: Fix NDR error 550 5.7.700 through 550 5.7.750 in Exchange Online
- Outlook.com Postmaster: Troubleshooting
- Yahoo Sender Hub: SMTP error codes
- Mimecast: Rejected and deferred message codes
Written by the Map Extract editorial team. Found an error? Email support@mapextract.uk and we will check and correct it. How we research guides: editorial policy.