Error map
spam folder Emails land in Gmail spam: SPF softfail, no DKIM or unauthenticated sender (“Be careful with this message”)
Email / SMTP · layer 2, Network
Centre: this error. First ring: errors it is linked with (9). 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 (9)
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.
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…
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…
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.
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.
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.
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.
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.
Email provider suspended or throttled your account: bounce rate too high (hard bounces from invalid addresses)
Your sending service paused your account because too many messages bounced.
Two steps away (26)
550 5.7.26 This mail has been blocked because the sender is unauthenticated (SPF/DKIM/DMARC)
Gmail/Outlook rejected the message because SPF and DKIM didn’t pass for the sender’s domain (DMARC failure).
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…
SPF: spf=permerror — Too many DNS lookups (limit is 10)
Your SPF record needs more than 10 DNS lookups to evaluate, so receivers treat SPF as a permanent error and the check fails.
ReplyError: NOAUTH Authentication required.
The Redis server requires a password (or ACL user) but the client didn’t authenticate.
Received disconnect: Too many authentication failures
Your SSH agent offered too many keys before the right one, and the server cut the connection (MaxAuthTries, default 6).
passwd: Authentication token manipulation error
passwd couldn’t update the password — the root filesystem is read-only, /etc/shadow has wrong permissions/attributes, or a PAM ru…
SMTP: 530 5.7.0 Must issue a STARTTLS command first / 530 5.7.1 Authentication required
The server will not accept mail until you encrypt the connection (STARTTLS) and/or authenticate, and your client did neither.
SMTP: 535 5.7.139 Authentication unsuccessful, basic authentication is disabled / SmtpClientAuthentication is disabled for the Tenant
Microsoft 365 turned off password-based SMTP AUTH for your mailbox or tenant; your client must use OAuth or the setting must be r…
SPF: spf=permerror — Multiple SPF records found for example.com
The domain publishes more than one TXT record starting with `v=spf1`; receivers must treat that as a permanent error.
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…
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.
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.
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…
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: 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.
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.
WordPress / PHPMailer: SMTP Error: Could not authenticate / SMTP connect() failed
The SMTP server rejected the login or couldn’t be reached — wrong credentials, app passwords required, wrong port/encryption, or…
550 5.7.1 Relaying denied / Message rejected as spam / Unauthenticated email not accepted
The receiving (or your outgoing) mail server refused the message — relaying isn’t allowed, the sender isn’t authenticated, or it…
SMTP: 450 4.7.1 <user@example.com>: Recipient address rejected: Greylisted, see http://postgrey.schweikert.ch/help/example.com.html
The recipient server deliberately rejected the first delivery attempt from an unknown sender (greylisting) and expects a legitima…
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.
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.
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.
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.
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.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError