Gmail error 550 5.7.26 ("unauthenticated email"): what does it mean and how do I fix it?
The 550 5.7.26 Gmail error means your message failed SPF or DKIM aligned with the From, so Gmail couldn't verify your domain sent it. Here's how to read the bounce, find the cause and fix your DNS records.
The 550 5.7.26 Gmail error means Gmail rejected your message because it couldn't verify your domain sent it: neither SPF nor DKIM passed aligned with the From, and your domain publishes DMARC or Gmail requires authentication. On Dongee hosting, mail leaves through MailChannels with SPF and DKIM, so the fix is usually your DNS or the sending app.
Below you'll see how to read the bounce, which causes are most common and how to fix it step by step, including how to authorize an app that sends on your behalf.
Updated November 22, 2026 · Dongee Team
What exactly does the 550 5.7.26 bounce say?
The error message usually comes in one of these two forms:
550-5.7.26 Unauthenticated email from yourdomain.com is not accepted due to domain's DMARC policy.
550-5.7.26 This mail has been blocked because the sender is unauthenticated. Gmail requires all senders to authenticate with either SPF or DKIM.How to read it:
- 550: permanent rejection. If you resend the same message, it will bounce again until you fix the cause.
- 5.7.26: the code says sender authentication failed.
- “due to domain's DMARC policy”: your domain has DMARC published and the message didn't pass SPF or DKIM aligned, meaning with the same domain that appears in the From.
- “Gmail requires all senders to authenticate”: the message carried no valid authentication at all, and Gmail requires it from senders.
What are the most common causes?
From most to least frequent:
- SPF doesn't include the server that actually sends. For example, you switched hosting and the record still authorizes the old one.
- DKIM isn't enabled, or the selector published in DNS doesn't match the one signing the messages.
- An app, CRM or form sends with a From on your domain without that service being authorized in SPF or signing with DKIM.
- Forwarding. When a message is forwarded, the forwarder's SPF no longer matches, and if the content was also altered, DKIM breaks.
- Two SPF records on the same domain. The specification invalidates both.
- A new domain with no SPF, DKIM or DMARC records.
- DMARC set to p=reject before checking that every legitimate source was authenticated.
How do I find the cause with “Show original”?
Send a test message to a Gmail account that does receive it, open the message menu and choose Show original. There you'll see the SPF, DKIM and DMARC results. For the full walkthrough, read the guide on how to check SPF, DKIM and DMARC with “Show original” in Gmail.
| Symptom in “Show original” | Likely cause | Fix |
|---|---|---|
| SPF: FAIL or SOFTFAIL | The outgoing server isn't in your SPF | Add your actual provider's include in a single SPF record |
| SPF: PERMERROR | Two SPF records or too many DNS lookups | Merge them into one and remove the includes you don't need |
| DKIM: missing or FAIL | DKIM disabled or wrong selector | Enable DKIM in your panel and publish the exact record it gives you |
| SPF/DKIM PASS, but for another domain | No alignment with the From (typical of apps and CRMs) | Set up your own sending domain in the external service |
| DMARC: FAIL with p=reject | Strict policy applied too early | Fix SPF/DKIM and temporarily drop to p=none while you measure |
How do I fix error 550 5.7.26 step by step?
- Check the original. Note what fails (SPF, DKIM or alignment) and which server appears in the “Received” headers.
- Fix SPF with a single record. Put every legitimate source in one TXT record. Generic example:
yourdomain.com TXT "v=spf1 include:spf.your-provider.example ~all"Use the include or value your provider or panel gives you. Don't copy the one in this example.
- Enable DKIM in the panel where your email lives and publish the record with the selector it shows you in your DNS. If your DNS is hosted somewhere else, copy it exactly.
- Publish DMARC starting at p=none so you can watch without blocking:
_dmarc.yourdomain.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com"When the reports show that everything passes, move up to quarantine and later to reject.
- Authorize the third parties that send on your behalf. Every CRM, newsletter platform or form must be listed in your SPF or, better yet, sign with DKIM using your domain.
- Wait for DNS to propagate and send a new test. Check again in “Show original” that SPF and DKIM show PASS and that DMARC passes.
What changes depending on where your email is hosted?
| Where your email is | How it goes out | What to check |
|---|---|---|
| Dongee shared hosting | MailChannels included for outgoing mail, with SPF and DKIM | That your domain's DNS has the SPF and DKIM your panel shows |
| Dongee Business Hosting | Through MailChannels if you set up the outgoing SMTP | The outgoing SMTP settings and the DNS records |
| Dongee Cloud | You manage the server; MailChannels is licensed separately | SPF, DKIM and DMARC for your own mail server or relay |
| Dongee Prime Email | Mailboxes with antispam and DKIM | Publish the DKIM and SPF it gives you; don't mix Prime Email and hosting mailboxes on the same domain |
| App on Dongee Live (Dongee's platform for publishing apps) | Outgoing SMTP over port 587 or 465 | That the app's From is the same mailbox or domain it authenticates with |
If the bounce comes from the outgoing server and not from Gmail, the problem may be something else: read the article on the MagicSpam 550 error when sending email. If Outlook or Hotmail also reject your messages, see the Outlook and Hotmail error 550 5.7.515, which has a similar cause.
What mistakes should you avoid?
- Publishing several SPF records, one per service. They must all go in a single record.
- Using “+all”, which authorizes any server in the world to send as your domain.
- Setting DMARC to p=reject without measuring first: you'll block your own legitimate mail.
- Resending the rejected message over and over: it doesn't fix anything and can hurt your domain's reputation.
Frequently asked questions
Does error 550 5.7.26 mean my domain is blacklisted?
No. It's an authentication failure, not a reputation block. You fix it by correcting SPF, DKIM and DMARC.
Is having only SPF or only DKIM enough?
To pass DMARC, one of the two has to pass and be aligned with the From, but it's best to have both. DKIM holds up better when messages are forwarded.
How long does the DNS change take to work?
It depends on your records' TTL and your DNS provider. It usually takes anywhere from a few minutes to a few hours. Wait, then send a new test.
Why do only the emails from my web form fail?
Because the form probably sends from another server using a From on your domain. Set it up to send through authenticated SMTP with a mailbox on your domain.
Can I get help checking my records?
Yes. Dongee offers 24/7 human support in your language (the platform translates on the fly), and the team can check your records with you by chat or WhatsApp, even if you aren't a customer yet.
In short, 550 5.7.26 means your email didn't prove where it came from. Keep a single correct SPF record, enable DKIM, publish DMARC starting at p=none and authorize every service that sends on your behalf. Once that's done, Gmail normally accepts your messages again.
Comenta lo que quieras
Unete a la charla
Solo ingresa tu email