Error map
bounce rate Email provider suspended or throttled your account: bounce rate too high (hard bounces from invalid addresses)
Email / SMTP · layer 2, Network
Centre: this error. First ring: errors it is linked with (11). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (11)
SendGrid: emails accepted (202) but never delivered — recipient is on the bounce/spam/unsubscribe suppression list
SendGrid returns success, but messages to some addresses are dropped because they're suppressed.
Email sent but never received and no bounce: silently dropped, quarantined or filtered
The sender sees "sent", the recipient sees nothing, and there is no error message.
Postmark: 406 Inactive recipient (error code 406) — address suppressed after a hard bounce or spam complaint
Postmark refuses to send to an address that previously hard bounced or complained, to protect your reputation.
Yahoo/AOL: 554 5.7.9 Message not accepted for policy reasons (spam content, authentication or reputation)
Yahoo rejects your mail for policy reasons, typically authentication or bulk sender requirements.
Sending IP listed on a DNS blocklist (Spamcop, Barracuda, SORBS, UCEPROTECT) — mail rejected or sent to spam
Your server's IP appears on one or more DNSBLs, so many receivers refuse or junk your mail.
Emails land in Gmail spam: SPF softfail, no DKIM or unauthenticated sender (“Be careful with this message”)
Messages are delivered, but Gmail puts them in spam or shows a warning banner because authentication fails.
Gmail/Yahoo bulk sender requirement: one-click unsubscribe (List-Unsubscribe-Post) missing
Marketing/bulk mail without RFC 8058 one-click unsubscribe headers gets throttled or sent to spam.
Amazon SES account under review or paused: bounce rate above 5% / complaint rate above 0.1%
SES placed your account on probation or paused sending because bounce or complaint rates passed its thresholds.
Reverse DNS (PTR) mismatch: forward-confirmed reverse DNS fails for the sending IP
The sending IP's PTR record doesn't resolve back to the same IP, so many servers reject or score down your mail.
Newsletter deliverability poor on a shared sending IP (other senders' reputation affects you)
Your campaigns land in spam or get throttled because neighbours on the same shared IP have a bad reputation.
New domain or IP: emails deferred or throttled until reputation builds (IP/domain warm-up)
A brand-new sending domain or IP gets throttled, deferred (4xx) or spam-foldered by large providers.
Two steps away (29)
SendGrid: 403 Forbidden — The from address does not match a verified Sender Identity. Mail cannot be sent until this error is resolved
SendGrid only sends from addresses or domains you have verified (single sender or domain authentication).
554 4.4.7 Message expired: unable to deliver in 840 minutes (delivery timeout)
The sending server kept retrying but the recipient server never accepted the message before the retry limit.
SendGrid: 401 Unauthorized / 403 Forbidden — API key invalid or lacking Mail Send permission
The SendGrid API or SMTP login rejects the key.
SMTP: 554 5.7.1 Message content rejected / Your message looks like spam (spam score exceeded)
The receiver's content filter scored your message as spam based on its text, links, headers or sender reputation and rejected it…
Gmail: 421 4.7.28 Our system has detected an unusual rate of unsolicited mail originating from your IP address
Gmail rate-limited your sending IP because it saw a spike or spam-like patterns.
550 5.1.1 The email account that you tried to reach does not exist (User unknown)
The recipient mailbox doesn’t exist on the receiving server — a typo in the address, a deleted account, or a wrong domain.
SMTP: 421 4.7.0 Our system has detected an unusual rate of unsolicited mail originating from your IP address. Mail sent from your IP address has been temporarily rate limited
The receiving server (often Gmail or Outlook) is temporarily throttling your mail because the volume or reputation of your sendin…
Bounce storm / backscatter: your server sends bounces to forged senders or bounces loop between servers
Mail systems send non-delivery reports to innocent people (forged senders) or bounce messages ping-pong endlessly.
Yahoo/AOL: 421 4.7.0 [TSS04] Messages from your IP temporarily deferred due to unexpected volume or user complaints
Yahoo deferred your mail because your IP's volume or complaint rate looks suspicious.
550 5.7.1 Message rejected due to organization policy (DLP, transport rule or content filter)
The recipient organization's mail policy blocked the message because of its content, attachments or sender.
554 5.5.1 Error: no valid recipients (all RCPT TO addresses were rejected)
DATA was attempted after every recipient was refused, so there's nothing valid to deliver to.
SMTP: 550 5.7.1 Service unavailable; Client host [203.0.113.5] blocked using zen.spamhaus.org
The receiving server checked your IP in a DNS blocklist (Spamhaus, Barracuda, SORBS…) and refused your mail because it is listed.
SMTP: 554 5.7.1 Service unavailable; Client host [203.0.113.5] blocked / 554 5.7.1 <mail.example.com>: Client host rejected: Access denied
The server refused the connection from your IP because it is blocked by policy, not in the allowed list, or listed on a blacklist.
Microsoft: 550 5.7.606 Access denied, banned sending IP (S3150/S3140 — IP reputation block)
Outlook.com/Microsoft 365 blocked your sending IP because of its reputation.
SMTP: 534-5.7.9 Application-specific password required. Learn more at https://support.google.com/accounts/answer/185833
The Google account has 2-Step Verification on, so SMTP clients cannot use the normal password; they need an app password (or OAut…
SPF: Received-SPF: softfail (google.com: domain of transitioning bounce@example.com does not designate 203.0.113.5 as permitted sender)
The server that sent the mail is not listed in the sender domain's SPF record, so the receiver marks it fail or softfail.
DMARC: dmarc=fail (p=REJECT) — SPF and DKIM pass but domains are not aligned with the From header
Authentication passed for another domain (your ESP's), but neither the SPF Return-Path domain nor the DKIM `d=` domain matches th…
SMTP: 535-5.7.8 Username and Password not accepted. Learn more at https://support.google.com/mail/?p=BadCredentials
The server received your login but rejected it — wrong username or password, an unusable password type, or a blocked sign-in.
Gmail: 550 5.7.32 Your email has been blocked because the From: header domain isn't aligned with SPF or DKIM
Gmail's bulk sender rules require the visible From domain to align with an authenticated SPF or DKIM domain.
Gmail Postmaster Tools: spam rate above 0.3% — mail delivered to spam or throttled
Too many recipients mark your mail as spam, so Gmail's reputation for your domain drops.
SES MessageRejected: Email address is not verified. The following identities failed the check in region
SES refused to send because the From address/domain isn’t verified — or the account is still in the SES sandbox, where recipients…
Amazon SES: Throttling — Maximum sending rate exceeded (454 Throttling failure)
You are sending faster than your Amazon SES account's per-second limit, so SES throttles the requests.
AWS CLI/SDK: SSL validation failed for https://... certificate verify failed (custom CA bundle / proxy)
The AWS CLI or SDK can't verify the endpoint's certificate, usually behind a TLS-inspecting proxy or with an outdated bundle.
SMTP: 550-5.7.25 The IP address sending this message does not have a PTR record setup, or the corresponding forward DNS entry does not point to the sending IP
Gmail (and others) require your sending IP to have a reverse DNS (PTR) record that resolves back to the same IP; yours has none o…
550 5.1.8 Sender address rejected: Domain not found (sender domain has no DNS A/MX)
The receiving server looked up the sender's domain and found no valid DNS record, so it rejected the message.
554 5.4.4 Unable to route: no MX or A record for the recipient domain / Host not found (HostNotFound)
The sending server can't find a mail route for the recipient's domain.
Mailgun: 403 Forbidden — Sandbox subdomains are for test purposes only. Please add your own domain or add the address to authorized recipients
You are sending from Mailgun's free sandbox domain, which only delivers to addresses you have manually authorized.
421 Service not available, closing transmission channel (SMTP server refused or dropped the connection)
The receiving server accepted the connection but immediately said it can't serve you now and closed it.
Microsoft 365: 451 4.7.500 Server busy, please try again later (throttling / reputation)
Exchange Online is delaying your mail because its capacity limits or your sending reputation triggered throttling.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError