Home » Blog » Fixing the “550-5.7.26 Unauthenticated Sender” Email Error

Fixing the “550-5.7.26 Unauthenticated Sender” Email Error

By /

If you’ve ever sent an email and received a frustrating bounce message like:

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

– don’t panic.
This error is common and usually easy to fix with a few DNS updates.

As a System Engineer, Web Developer in Toronto, I regularly help clients troubleshoot email deliverability problems. Whether you’re on cPanel, Cloudflare, GoDaddy, Plesk, or running your own VPS, this guide explains exactly how to resolve the 550-5.7.26 error and make sure Gmail trusts your messages again.

What the 550-5.7.26 Error Means

This bounce message means Gmail couldn’t verify that your email address is actually on your domain.
It checked your SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) settings, and both failed or were missing.

In simple terms, Gmail thought your message might be spoofed or forged, so it blocked it.

Why Authentication Matters

Email authentication prevents spammers from pretending to send emails from your domain.
The three main technologies you need are:

  • SPF (Sender Policy Framework): Lists which servers are allowed to send email for your domain.
  • DKIM (DomainKeys Identified Mail): Digitally signs messages to prove they weren’t altered.
  • DMARC (Domain-based Message Authentication, Reporting & Conformance): Tells mail servers what to do if SPF or DKIM fails.

If SPF or DKIM isn’t set up correctly, Gmail and other mail providers (Outlook, Yahoo, etc.) will reject your emails with a 550-5.7.26 error.

How to Fix the 550-5.7.26 Error

Below are step-by-step fixes for every major hosting scenario.

For cPanel Users

If you’re using cPanel (common for shared or reseller hosting):

Follow the steps:

1: Log in to your cPanel dashboard (yourdomain.com/cpanel).
2: Go to Email Deliverability.
3: Click Manage next to your domain.
4: If DKIM or SPF shows errors, click “Install the Suggested Record” for both.
5: Save your changes.

Wait 1–2 hours for DNS propagation, then send a test email to Gmail.
Open the message → click ⋮ (three dots) → Show Original → confirm:

SPF: PASS
DKIM: PASS

For Domains Managed on Cloudflare, GoDaddy, or Other DNS Providers

If your domain’s DNS is managed outside cPanel, for example, through Cloudflare, GoDaddy, Namecheap, or Google Domains, cPanel cannot automatically publish SPF and DKIM records.
You’ll need to copy them manually.

Step 1: Generate Records in cPanel

  1. Go to Email Deliverability in cPanel.
  2. Click Manage next to your domain.
  3. Copy the Suggested SPF and DKIM TXT records.

Step 2: Add Records in Your DNS Provider

Cloudflare
  1. Log in to Cloudflare → DNS → Records → Add Record
  2. Add DKIM record
    • Type: TXT
    • Name: default._domainkey
    • Content: paste DKIM from cPanel
    • Proxy: DNS Only (gray cloud)
  3. Add SPF record
    • Type: TXT
    • Name: @
    • Content: v=spf1 +a +mx include:_spf.hostexample.com ~all
    • Proxy: DNS Only
GoDaddy / Namecheap / Google Domains
  1. Log in to your account → manage DNS → add new TXT records.
  2. Add SPF and DKIM exactly as cPanel shows.
  3. Save and allow propagation (usually within 30–60 minutes).

Step 3: (Optional) Add a DMARC Record

Name: _dmarc
Type: TXT
Value: v=DMARC1; p=none; rua=mailto:postmaster@example.com;

Step 4: Test

After DNS updates, send a test email to Gmail and check for SPF: PASS and DKIM: PASS.

Never proxy TXT records (orange cloud) in Cloudflare, as it breaks mail authentication.

How Plesk Users Can Fix the 550-5.7.26 Email Error

If your hosting uses Plesk (common for Windows and VPS hosting):

Follow the step:

1: Log in to your Plesk dashboard.
2: Go to Mail → Mail Settings → [Your Domain].
3: Check Enable DKIM spam protection → enable “Use DKIM for signing outgoing mail.”
4: To configure SPF, open Domains → DNS Settings, then add this TXT record:

v=spf1 +a +mx include:_spf.hostexample.com ~all

Step 5: Apply changes and wait for DNS propagation.

Send a test email and verify that both SPF and DKIM show PASS in Gmail.

How VPS or Dedicated Server Users Can Fix the 550-5.7.26 Email Error

If you manage your own server (Postfix, Exim, or similar), you’ll need to configure SPF and DKIM manually.

SPF Record Example

In your DNS:

v=spf1 ip4:203.0.113.12 include:_spf.mailprovider.com ~all

DKIM Setup

  1. Install DKIM software (e.g., OpenDKIM for Postfix).
  2. Generate a key pair and publish the public key in DNS as a TXT record: default._domainkey IN TXT "v=DKIM1; k=rsa; p=MIGfMA0GCSq..."
  3. Link DKIM to your mail server configuration.

DMARC (Recommended)

v=DMARC1; p=none; rua=mailto:postmaster@example.com;

Restart your mail service and test using Mail-Tester or MXToolbox.

Testing and Verification Tools

Use these free tools to check your configuration:

Your test should show:

SPF: PASS
DKIM: PASS
DMARC: PASS (if configured)

Tips to Avoid Future Issues

  • Keep only one SPF record per domain.
  • Re-generate SPF/DKIM if you move your website or email hosting.
  • Always set Cloudflare DNS records for mail to DNS Only.
  • Use DMARC for added protection and reputation monitoring.

The “550-5.7.26 unauthenticated sender” error may look intimidating, but it’s usually caused by missing or incorrect SPF and DKIM records.
Once you properly authenticate your domain, Gmail and other email providers will accept your messages without issue.

As a System Engineer and Web Developer in Toronto, I always emphasize that technical credibility is just as important as visual design. A well-designed website builds trust, but reliable, authenticated email communication keeps that trust alive.

If you’re unsure about DNS settings or mail configuration, reach out to a professional or simply contact me. Getting it right the first time saves hours of frustration and ensures your messages always land safely in the inbox.

Scroll to Top