550 5.7.26: Gmail blocked unauthenticated email
Quick fix
Add the sending service to your SPF record and turn on DKIM signing with your own domain in that service. Then publish a DMARC record (p=none is enough for Gmail's bulk sender rule) with SPF or DKIM aligned to the From domain.
How to fix it
- Find the service that sent the rejected message (the bounce names the sending IP) and the domain in its From address.
- Add that service to your SPF record with the include or IP range it documents, and keep the record under 10 DNS lookups.
- Turn on DKIM signing with your own domain in that service and publish its key.
- Publish a DMARC record (
p=noneis enough for Gmail's bulk sender rule) and make sure SPF or DKIM aligns with the From domain. - Send a new test message to a Gmail address and check "Show original": SPF, DKIM and DMARC should all show PASS.
Learn more: DMARC explained: policy, alignment and reports
How to check
The email security check looks up SPF, DKIM, DMARC and MX for the domain in the From address in one report. For the SPF variant, also compare the IP address in the bounce with the senders your SPF record allows.
The Email security check opens with your domain filled in; it runs when you press Check.
Tools to check it
What the error means
550 5.7.26 is Gmail's permanent rejection for mail that is not authenticated the way Gmail requires. Gmail requires all senders to authenticate with SPF or DKIM; senders of close to 5,000 messages a day or more to personal Gmail accounts also need SPF, DKIM and DMARC, with the From domain aligned to SPF or DKIM. The text after the code tells you which check failed.
Google's list of Gmail SMTP errors has three 550 5.7.26 texts:
- "This email has been blocked because the sender is unauthenticated. Gmail requires all senders to authenticate with either SPF or DKIM." The message passed neither SPF nor DKIM.
- "The (E)MAIL FROM domain [domain-name] has an SPF record with a hard fail policy (-all) but it fails to pass SPF checks with the ip: [ip-address]." The sending IP is not in your SPF record, which ends in
-all. - "Unauthenticated email from domain-name is not accepted due to domain's DMARC policy." The From domain has an enforcing DMARC policy and the message had no aligned SPF or DKIM pass; see DMARC quarantine vs reject.
Nearby codes on the same list: 550 5.7.27 (did not pass SPF, for bulk senders), 550 5.7.30 (did not pass DKIM) and 550 5.7.40 (the sending domain has no DMARC record or no DMARC policy). The requirements apply since February 2024, and Google writes that "Starting November 2025, Gmail is ramping up its enforcement on non-compliant traffic", including temporary and permanent rejections.
Sources
- Google: Gmail SMTP errors and codes (checked 2026-11-15)
- Google: Email sender guidelines (checked 2026-11-15)
- Google: Email sender guidelines FAQ (checked 2026-11-15)