Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Email delivery

Gmail rejects your mail with 550 5.7.26: no authentication information

Error550-5.7.26 This message does not have authentication information or fails to pass authentication checks

Short answer

Gmail returns 5.7.26 when a message is not authenticated. Every sender needs SPF or DKIM, and bulk senders over 5,000 messages a day need SPF, DKIM and DMARC. The usual causes are a sending service missing from SPF, DKIM not turned on, a DKIM key shorter than 1024 bits, or a missing DMARC record.

  • Applies to Gmail sender guidelines, SPF, DKIM, DMARC
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Read the authentication results Gmail recorded. Check the DNS records Gmail will look up for your sending domain, and compare them with what the cause list below says each record must contain.

    dig +short TXT example.com
    dig +short TXT _dmarc.example.com
  2. 2Match what you see, then jump to its fix

    1. 1Your sending service does not appear in the domain's SPF record.The sending service is missing from the SPF recordFix
    2. 2The sending service has no DKIM key published for your domain.DKIM is not enabled for the sending domainFix
    3. 3DKIM is published, but Gmail does not accept it.The DKIM key is too shortFix
    4. 4You send more than 5,000 messages a day to Gmail, or DMARC shows fail although SPF or DKIM pass.Bulk sender without DMARC, or From domain does not alignFix

What does the error look like?

  • 550-5.7.26 This message does not have authentication information or fails to pass authentication checks
  • rejected with a 5.7.26 error

Cause 1 of 4

The sending service is missing from the SPF record

1Check

Google says to publish an SPF record that lists every sender allowed to use the domain. A third-party sender left out of the record is more likely to be flagged.

dig +short TXT example.com

2Fix

Add the include your sending service documents to the single SPF record. Do not publish a second SPF record.

v=spf1 include:sender.example.net ~all

3Verify

Send a new test message and see an SPF pass in the message headers.

dig +short TXT example.com

Confirmed by support.google.com

Did this fix it?

Cause 2 of 4

DKIM is not enabled for the sending domain

1Check

Gmail requires SPF or DKIM from every sender and recommends signing with DKIM. If you use an email service provider, confirm it signs with your domain.

dig +short TXT selector1._domainkey.example.com

2Fix

Turn on DKIM signing for your domain at your sending provider and publish the key record in DNS exactly as the provider shows it.

selector1._domainkey.example.com  TXT  "v=DKIM1; k=rsa; p=PUBLIC_KEY_FROM_PROVIDER"

3Verify

The message headers show a DKIM pass for your domain.

dig +short TXT selector1._domainkey.example.com

Confirmed by support.google.com

Did this fix it?

Cause 3 of 4

The DKIM key is too short

1Check

Gmail requires a DKIM key of at least 1024 bits and recommends 2048 bits.

dig +short TXT selector1._domainkey.example.com

2Fix

Generate a 2048-bit key at your provider, publish it under a new selector and switch signing to it.

# publish the new TXT record, then switch the signing selector at the provider

3Verify

A new message shows a DKIM pass with the new selector.

dig +short TXT newselector._domainkey.example.com

Confirmed by support.google.com

Did this fix it?

Cause 4 of 4

Bulk sender without DMARC, or From domain does not align

1Check

Bulk senders need SPF, DKIM and DMARC. A message passes DMARC when SPF or DKIM authenticates it and the authenticating domain matches the From: header domain.

dig +short TXT _dmarc.example.com

2Fix

Publish a DMARC record, start with a monitoring policy and a report address, and make the sending service sign with your own domain.

_dmarc.example.com  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@example.com"

3Verify

The message headers show a DMARC pass.

dig +short TXT _dmarc.example.com

Confirmed by support.google.com

Did this fix it?

How do I stop it coming back?

  • List every sending service in one SPF record when you add it, and enable its DKIM at the same time.
  • Publish DMARC with report addresses and read the reports.
  • Use 2048-bit DKIM keys.
  • Check the domain with Google Admin Toolbox and watch delivery in Postmaster Tools.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Related fixes

Email

Mail from your own domain keeps landing in the spam folder

dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=example.com

Open a message that went to spam and read its Authentication-Results header: it shows whether SPF, DKIM and DMARC passed, and for which domain.

5 causes, each with a fix

Email

Django send_mail fails or hangs with an SSL error

smtplib.SMTPException raised from send_mail()

Django has two secure modes that must not be mixed: EMAIL_USE_TLS for explicit TLS (STARTTLS, usually port 587) and EMAIL_USE_SSL for implicit TLS (usually port 465).

4 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.