Error map
BIMI BIMI logo not displayed in Gmail/Yahoo: DMARC enforcement, SVG Tiny PS or VMC certificate problem
Email / SMTP · layer 2, Network
Centre: this error. First ring: errors it is linked with (8). 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 (8)
DMARC: dmarc=none (no DMARC record found for example.com) — bulk sender requirements not met
The sender's domain publishes no `_dmarc` TXT record, so receivers cannot apply any policy; Gmail and Yahoo now require one for b…
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).
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…
DMARC p=reject blocking your own legitimate mail from third-party senders (CRM, newsletter, helpdesk)
After moving to `p=reject`, mail from tools sending on your behalf bounces or lands in spam because they aren't aligned.
DMARC record invalid: syntax error, wrong tag order or multiple records (v=DMARC1 must be first)
Receivers ignore your DMARC record because it isn't valid, so no policy is enforced.
550 5.7.1 Unauthenticated email is not accepted due to the domain's DMARC policy (p=reject)
The recipient rejected your message because the From domain publishes `p=reject` and your mail failed SPF/DKIM alignment.
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.
Forwarded or mailing-list mail fails DMARC: ARC chain missing or failed (arc=fail)
A message forwarded through a list or forwarding service loses SPF/DKIM alignment, and the ARC seal can't rescue it.
Two steps away (20)
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.
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.
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: 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…
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…
DMARC reports not arriving: external destination domain didn't authorise reports (_report._dmarc record)
You send DMARC reports (rua/ruf) to a mailbox on another domain, which must publish a verification record.
500 5.5.1 Command unrecognized / Syntax error, command unrecognized
The server didn't understand a command the client sent, often because it spoke the wrong protocol or the wrong mode.
501 5.1.7 Bad sender address syntax (invalid MAIL FROM)
The sender address in MAIL FROM isn't a valid address.
501 5.5.4 Syntax error in parameters or arguments (invalid SMTP command argument)
A command argument (HELO name, MAIL FROM, RCPT TO or AUTH data) didn't match the expected syntax.
Azure AD (Entra ID): AADSTS700016 Application not found in the directory
The client ID in your sign-in request doesn’t exist in the tenant you’re authenticating against.
Azure AD (Entra ID): AADSTS50076 / AADSTS50079 — multi-factor authentication required
A Conditional Access policy requires MFA, but the sign-in flow (often a script, legacy client or ROPC password grant) can’t compl…
ReplyError: NOAUTH Authentication required.
The Redis server requires a password (or ACL user) but the client didn’t authenticate.
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.
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…
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.
DKIM: body hash did not verify — message modified after signing (footers, mailing list, line wrapping)
The signature's body hash doesn't match the received body, because something changed the content after DKIM signing.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError