Error map
DKIM: body hash did not verify DKIM: dkim=fail (body hash did not verify) / signature verification failed
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)
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: 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…
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.
DKIM: dkim=permerror (no key for signature) / key not found in DNS selector._domainkey
The message is signed with a selector, but the receiver found no DKIM public key in DNS at that selector, so verification cannot…
Laravel: SQLSTATE[HY000] [2054] The server requested authentication method unknown to the client [caching_sha2_password]
The PHP MySQL driver doesn't support the authentication plugin MySQL 8 uses (`caching_sha2_password`).
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…
IMAP: NO [AUTHENTICATIONFAILED] Invalid credentials (Failure)
The IMAP server rejected the login — wrong password, IMAP disabled, an app password required, or basic auth blocked.
Two steps away (23)
PHP mail() returns false / emails not delivered
PHP’s mail() function failed or emails never arrive (spam or rejected).
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…
Contact Form 7: There was an error trying to send your message. Please try again later.
The form submitted, but wp_mail() failed to send — the server can’t send mail or the mail settings are wrong.
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…
WordPress REST API: {"code":"rest_forbidden","message":"Sorry, you are not allowed to do that."} (401/403)
The REST request isn’t authenticated or the user lacks the capability required by the route’s permission_callback.
Laravel: Symfony\Component\Routing\Exception\RouteNotFoundException: Route [login] not defined
Code called route('name') for a route name that doesn’t exist — very often route('login') from the auth middleware in API-only ap…
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…
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…
SMTP: 553 5.7.1 <noreply@example.com>: Sender address rejected: not owned by user user@example.com
The SMTP server only lets an authenticated user send as addresses they own, and the From/envelope sender does not match the login.
SMTP: 550 5.4.5 Daily user sending quota exceeded (Gmail)
The Gmail or Google Workspace account reached its 24-hour sending limit, so it stops accepting outgoing mail until the limit rese…
cURL error 6: Could not resolve host: api.example.com
PHP cURL couldn’t resolve the hostname via DNS.
sudo: unable to resolve host <hostname>: Name or service not known
The machine’s hostname isn’t in /etc/hosts (or DNS), so sudo prints this warning — usually after changing the hostname.
ping: google.com: Temporary failure in name resolution
The Linux host can’t resolve domain names — no working DNS server is configured or reachable.
Python: smtplib.SMTPAuthenticationError: (535, b'5.7.8 Username and Password not accepted')
`smtp.login()` was rejected by the server — wrong credentials, wrong password type, or authentication not allowed for that accoun…
Nodemailer: Error: Invalid login: 535-5.7.8 Username and Password not accepted (code: 'EAUTH', responseCode: 535)
The SMTP server rejected the credentials passed to Nodemailer.
Postfix: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
Postfix could not authenticate a user (inbound) or could not log in to a relay (outbound) because the SASL service or credentials…
SMTP: 451 4.3.0 Error: queue file write error / 451 Requested action aborted: local error in processing
The server hit an internal problem (disk, database, content filter, DNS) while handling your message and asked you to retry later.
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.
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.
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.
IMAP: NO [ALERT] Too many simultaneous connections. (Failure)
The server limits concurrent IMAP sessions per account and your clients (phone, laptop, scripts) opened more than allowed.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError