In short. Gmail is delaying or rejecting your emails: they arrive late, land in spam, or never reach your customers who use Gmail. The code in the error message tells you which of your domain's authentication settings (SPF, DKIM or DMARC) is missing or wrong. The fix is made in your domain's DNS and in the tool that sends your emails: by you or your IT provider. Google says a new SPF record can take up to 48 hours to start working.
When Gmail rejects an email for failing authentication, the error message starts with a code. 5.7.26: the email is unauthenticated or fails the domain's DMARC policy. 5.7.27: it fails SPF. 5.7.30: it fails DKIM. 5.7.32 or 4.7.32: SPF or DKIM pass, but not with the sender's domain. A 4.7.x code means Gmail is slowing your sends down; a 5.7.x code means it is rejecting them.
Last checked: November 18, 2026, in Gmail's official list of SMTP errors (updated November 10, 2026).
The codes and their exact text
Gmail returns these texts in English, whatever the sender's language.
| Code | Gmail's text (excerpt) | What to fix |
|---|---|---|
550 5.7.26 | "This email has been blocked because the sender is unauthenticated." or "Unauthenticated email from domain is not accepted due to domain's DMARC policy." | SPF and DKIM both fail, or DMARC fails |
550 5.7.27 | "This message was blocked because it didn't pass SPF authentication." | SPF |
550 5.7.30 | "This message was blocked because it didn't pass DKIM authentication." | DKIM |
421 5.7.32 | "Your email was blocked because the From: header (RFC5322) in this message isn't aligned with either the authenticated SPF or DKIM organizational domain." | alignment |
421 4.7.26 | "This email has been rate limited because it is unauthenticated. Gmail requires all senders to authenticate with either SPF or DKIM." | SPF or DKIM (sends slowed down) |
421 4.7.27, 4.7.30, 4.7.32 | "Your email has been rate limited because…" (SPF, DKIM or alignment) | same thing, sends slowed down |
550 5.7.25 | "…the sending IP address doesn't have a PTR record…" | the sending server's reverse DNS (host side) |
550 5.7.29 | "This message was blocked because it wasn't sent over a TLS connection." | the sending server's encryption |
The 5.7.26 text can also state that the domain has a strict SPF failure (-all) and that the sending IP address is not listed in it.
Gmail's rules, in brief
- All senders must pass SPF or DKIM. That is what the
4.7.26text says. - Bulk senders must pass SPF and DKIM, have a DMARC record, and align the sender address. That is what the
5.7.27,5.7.30and5.7.32texts say.
The details and thresholds are on our page about the Gmail and Yahoo sender requirements.
Step 1: identify the service that sends
Does the rejected message come from your mailbox provider (Google Workspace, Microsoft 365, web host) or from a tool (newsletter, CRM, invoicing, website)? Each service has its own settings: fix the one that sends the rejected message.
Step 2: fix according to the code
5.7.27or4.7.27(SPF): add the service to your SPF, without creating a second record. See our SPF guides.5.7.30or4.7.30(DKIM): turn on DKIM signing with your domain in the service. See our DKIM guides.5.7.32or4.7.32(alignment): the service signs or sends with its own domain. Set up a custom sending domain in the tool, so the DKIM signature carries your domain.5.7.26: publish a DMARC record if it is missing, then fix SPF and DKIM as above. See our DMARC guides.5.7.25(PTR) and5.7.29(TLS): these settings belong to the sending server. With a sending service, contact its support; with your own server, your host.
Step 3: check
Send a test message to a Gmail mailbox, open it, choose Show original, and check for PASS next to SPF, DKIM and DMARC. Our free tools SPF check, DKIM check and DMARC check check the records from the Internet.
Check your domain for free. AttackScout reads your SPF, your DKIM and your DMARC from the Internet and tells you which one is getting your emails rejected. In one minute, no account. Check my domain
Frequently asked questions
Gmail is slowing my sends (4.7.x) but eventually delivers them. Do I need to act?
Yes. The slowdown signals the same flaw as the rejection. Fix it before your sends get blocked.
The error mentions a "temporary DNS failure" (4.7.26 as a 451).
Gmail could not read your DNS records at that moment. Check that your DNS is answering correctly; if the error does not come back, it was just a one-off incident.
Our emails get through to Outlook but not to Gmail.
Each mailbox provider applies its own thresholds. Fix SPF, DKIM and DMARC once and for all: both will be satisfied. See also Outlook's 550 5.7.515 error.
Sources
Accessed on November 18, 2026.
- Google Workspace, Gmail SMTP errors and codes (updated November 10, 2026): https://knowledge.workspace.google.com/admin/support/troubleshooting/gmail-smtp-errors-and-codes
- Google, Email sender guidelines (accessed on November 12, 2026; English version checked on November 18, 2026): https://support.google.com/mail/answer/81126?hl=en
- IETF, RFC 7489 (DMARC, alignment): https://www.rfc-editor.org/rfc/rfc7489