Senderward

550 5.7.26 and 5.7.515: why Gmail and Outlook reject your mail

Updated

Both errors mean the same thing: the receiver could not tie the message to your domain with SPF, DKIM and DMARC, and refused it. Gmail answers 550 5.7.26, Outlook.com answers 550 5.7.515. The fix is almost always in DNS or in the settings of the service that sent the mail.

The error texts

Gmail: 5.7.26

Gmail uses 5.7.26 for two situations. The bounce text tells you which:

The same code with a 4 in front (421 4.7.26, 451 4.7.26) is the temporary version: Gmail rate limits or defers the mail and the sending server retries. Related codes: 5.7.27 (SPF did not pass) and 5.7.25 (the sending IP has no PTR record). Since November 2025 Gmail enforces its sender requirements with rejections, so these show up more often.

Outlook.com: 5.7.515

550 5.7.515 Access denied, sending domain <domain> does not meet the required authentication level.

Microsoft rejects mail like this to its consumer accounts (Outlook.com) from domains that send 5,000 or more messages there, unless SPF and DKIM both pass and DMARC passes with alignment. Unlike Gmail, one of SPF or DKIM is not enough.

The four usual causes

1. A service sends as you without authentication

A new CRM, newsletter tool or helpdesk sends with From: [email protected], but it signs DKIM with its own domain and uses its own bounce domain for SPF. Nothing passes for example.com.

Fix: set up domain authentication at that service. It gives you DKIM records (usually CNAMEs like s1._domainkey.example.com) to publish. DKIM for your domain is enough for DMARC and survives forwarding.

2. SPF and DKIM pass, but not aligned

The message passes SPF for bounces.example.org and DKIM for example.org, but the From: header says example.com. DMARC needs at least one of them to match the From: domain (or a subdomain of it, with the default relaxed alignment).

Fix: same as above: DKIM signed with d=example.com, or a custom return-path such as bounce.example.com that the service supports.

3. SPF breaks

SPF fails with a permanent error when the record needs more than 10 DNS lookups, or when there are two SPF records. Then every message that relies on SPF alone fails.

Fix: one v=spf1 record, at most 10 lookups (include:, a, mx, redirect= and nested includes all count). Remove services you no longer use, and rely on DKIM for the rest.

4. Forwarding

Your mail reaches Gmail through a forwarder (an alias, an old address, a list). SPF fails because the forwarder's IP is not yours. If the forwarder also changed the message, DKIM fails too, and with p=reject Gmail rejects it. The bounce then comes back to you from the forwarder.

Fix: make sure your mail is DKIM signed, since that survives forwarding when the message is not changed. If you run the forwarder, rewrite the envelope sender (SRS) and do not modify forwarded messages. If you are the recipient, deliver to Gmail directly or use a forwarder that adds ARC headers.

How to find which one it is

  1. Send a test message from the same service to a Gmail account you control (if Gmail accepts it), open it and choose "Show original". Gmail shows SPF, DKIM and DMARC as PASS or FAIL with the domain each was checked for.
  2. In the Authentication-Results header, compare header.from with smtp.mailfrom (SPF) and header.i or header.d (DKIM). If neither matches your domain, it is cause 1 or 2.
  3. If SPF says permerror, it is cause 3.
  4. If only forwarded mail bounces, it is cause 4.
  5. Your DMARC aggregate reports show the same per sending IP, for all mail at once. See How to read DMARC aggregate reports.

For the requirements behind these errors, see Gmail, Yahoo and Microsoft sender requirements.

Check your domain

Free email security check by Lookproof. Opens on lookproof.dev.

Senderward checks your domain's DMARC, SPF, DKIM, MX, MTA-STS and TLS-RPT every day and emails you, with the fix, when something gets worse. $7 per domain per month, 14 days free. See pricing

Sources