Error codes
Gmail SMTP bounces from Google's error list, last updated 18 September 2026 UTC, plus SPF permerror as RFC 7208 defines it.
Each page quotes one row from Google's SMTP error list (18 September 2026 UTC). The title is the code and cause, not the full bounce text.
One enhanced status can map to several pages: `550 5.7.1` covers IPv6 PTR, a missing From header, and direct-to-Gmail IP; `421` variants are the rate-limited twins where Google lists them. SPF permerror and the ten-lookup cap come from RFC 7208; DMARC alignment from RFC 7489.
/
Gmail error 550 5.7.26: unauthenticatedGmail 550 5.7.26 means the sender was not authenticated. Google requires SPF or DKIM. The SMTP error list of 18 September 2026 UTC prints three blocks. SPF PermErrorPermError means the published SPF records could not be correctly interpreted. RFC 7208 says that needs DNS operator intervention, not a later retry. DMARC alignment failedSPF or DKIM can pass on a domain that is not the From domain. DMARC still fails. RFC 7489 treats alignment as a separate check against From. SPF too many lookupsSPF evaluation must stop at 10 DNS-querying terms. Past that, RFC 7208 says the result is permerror. ip4 and ip6 do not spend one of those 10. Gmail error 550 5.7.27: SPF did not passGmail 550 5.7.27 means SPF did not pass. Bulk senders have to authenticate with SPF. The quoted row is Google's SMTP error list of 18 September 2026 UTC. Gmail error 550 5.7.30: DKIM did not passGmail 550 5.7.30 means DKIM did not pass. Bulk senders have to authenticate with DKIM. The quoted row is Google's SMTP error list of 18 September 2026 UTC.