Opens in a new tab

Gmail 550 5.7.30: the message didn’t pass DKIM authentication

Gmail requires bulk senders to sign their mail with DKIM, and this message carried no signature that verified: it was not signed, the key was not found in DNS, or the message changed after signing.

550 5.7.30 This message was blocked because it didn't pass DKIM authentication. Gmail requires bulk email senders to authenticate their email with DKIM. Authentication results: DKIM = did not pass To set up DKIM for your sending domains, visit Set up DKIM. 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.30 Your email has been rate limited because DKIM authentication didn't pass for this message. Gmail requires all email bulk senders to authenticate their email with DKIM. Authentication results: DKIM = Did not pass. To set up DKIM for your sending domains, visit Set up DKIM. To learn more about Gmail requirements for bulk email senders, visit Email sender guidelines. - gsmtp
Code550 5.7.30
Sent byGmail
TypePermanent — not retried
CauseDKIM

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

DKIM puts a signature in the message header that the receiver checks against a public key in the sender’s DNS. “Did not pass” covers all the ways that can go wrong — no signature, a missing or wrong key, or a body altered in transit.

The 421 4.7.30 version is temporary; the sending server retries.

Why it happens

  • DKIM was never turned on in the service that sent the message.
  • The DNS record for the selector was deleted, mistyped, or points at the wrong place (a CNAME with a doubled domain is common).
  • A key rotated in the service but not updated in DNS.
  • A gateway or mailing list that rewrites the message body or subject after it was signed.

How to fix it

  1. Check your domain below to see which DKIM keys it publishes.
  2. In the service that sent the message, set up DKIM for your domain and publish exactly the records it shows.
  3. If a key is published but still fails, look for something between the sender and Gmail that changes the message — a footer added by a gateway is typical.

Find every DKIM key your domain publishes →

DKIM setup for each sending service →

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