Opens in a new tab

Gmail 5.7.32: the From header isn’t aligned with the SPF or DKIM domain

Authentication passed, but for the wrong domain. Gmail requires bulk senders to align: the domain in the From address must match the domain that passed SPF or signed with DKIM. Here neither did.

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. Learn more about DMARC alignment. To learn more about Gmail requirements for bulk email senders, visit Email sender guidelines. - gsmtp
1 other wording of the same rejection

Temporary:

421 4.7.32 Your email has been rate limited because the From: header (RFC5322) in this message isn't aligned with either the authenticated SPF or DKIM organizational domain. Learn more about DMARC alignment. To learn more about Gmail requirements for bulk email senders, visit Email sender guidelines. - gsmtp
Code550 5.7.32
Sent byGmail
TypePermanent — not retried
CauseDMARC

Check your domain’s SPF, DKIM and DMARC

Enter the domain in your From address. We read its records the way Gmail does.

What it means

A message can pass SPF for a service’s own bounce domain (say, a mail provider’s) and pass DKIM for the service’s own signing domain, and still fail alignment, because neither is your domain. DMARC — and Gmail’s bulk-sender rules — only count authentication that aligns with the From address.

Google lists the permanent code with a 421 prefix on its own reference page; mail servers report it however they receive it. The temporary 4.7.32 is retried.

Why it happens

  • A sending service that signs with its own domain because domain authentication was never completed for yours.
  • A service whose bounce address is its own domain, and no DKIM for your domain — SPF passes, but not for you.
  • Sending with a From address on a domain other than the one you authenticated (a second brand, a subdomain with strict alignment).

How to fix it

  1. Complete domain authentication (DKIM for your domain) in the service that sent the message — that aligns it regardless of the bounce domain.
  2. Check your DMARC record below: adkim=s or aspf=s demand an exact match, and break subdomain setups that relaxed alignment would accept.

DKIM setup for each sending service →

Check the DMARC record and its alignment tags →

Sources

Message text and meaning checked on 25 September 2026 against these official sources:

Catch it before the bounces start

Add your domain and we monitor what these bounces are about — SPF, DKIM, DMARC, your sending servers on the blocklists, Gmail’s spam rate — every day, and email you the day something changes. Free for your first domain.

Create a free account