Gmail 550-5.7.26: "the sender is unauthenticated"

Gmail rejects mail that passes neither SPF nor DKIM, or fails your DMARC policy. How to find the failing service and fix it.

The bounce looks like one of these:

550-5.7.26 Your email has been blocked because the sender is unauthenticated.
550-5.7.26 Gmail requires all senders to authenticate with either SPF or DKIM.

550-5.7.26 Unauthenticated email from example.com is not accepted due to
550-5.7.26 domain's DMARC policy.

Both mean Gmail could not confirm that the message really came from the domain in the From address. The first variant says neither SPF nor DKIM passed. The second says the domain publishes a DMARC policy of quarantine or reject, and the message failed DMARC.

Why it happens

  • A service sends as your domain but isn't set up. A new CRM, helpdesk, invoicing tool or website form sends with your address in From, but your SPF record doesn't list it and it doesn't sign with DKIM for your domain.
  • SPF breaks. The record exceeds 10 DNS lookups, there are two SPF records, or it has a syntax error. Receivers then treat SPF as failed for every message.
  • SPF and DKIM pass, but for the wrong domain. Your email service passes SPF for its own bounce domain, which does not count for DMARC. See DMARC alignment.
  • The message was forwarded or modified. Forwarding breaks SPF, and changes to the body break DKIM. See forwarding and mailing lists.
  • Someone else is sending as you. If you don't recognise the mail at all, Gmail is doing exactly what your DMARC policy asks.

How to fix it

  1. Find out which service sent the bounced message. The bounce usually contains the sending IP address; the headers of a sent copy show the rest.
  2. Turn on DKIM signing for your domain in that service. Every serious email platform supports it: you publish one or more CNAME or TXT records they give you.
  3. If the service uses your domain in the envelope sender (Return-Path), add it to your SPF record. Most marketing platforms use their own bounce domain, in which case DKIM alone is what makes DMARC pass.
  4. Send a new test message and check the Authentication-Results header: you want dmarc=pass.

Don't lower your DMARC policy to p=none to make the bounces stop, unless you have no idea yet which services send for you. It also lets every forged message through.