Blazalek.com

4.7.26SMTP 4.7.26: Gmail unauthenticated-mail rate limit

Gmail's accepted 4.7.26 response temporarily rate-limits a message because SPF and DKIM authentication did not pass. Preserve the diagnostic, repair the verified authentication path, and retry at a reduced pace.

Category
Security, authentication and policy
Class
Temporary failure
Retry
Controlled retry
Suppression
Check the full context

TL;DR

Gmail 4.7.26 is a temporary unauthenticated-mail rate limit. In the accepted capture, verify that both SPF and DKIM did not pass from the exact reply and logs, correct the responsible configuration, reduce rate, and retry with backoff; it is not a recipient hard bounce.

What this code means

The accepted Gmail response says it has rate-limited unauthenticated mail and requires senders to authenticate with either SPF or DKIM. The concrete code is published from exact Gmail evidence, not from a confirmed IANA registration for this detailed pattern, and the response does not establish a recipient-address failure.

Provider examples

Gmail example
4.7.26 This mail has been rate limited because it is unauthenticated. Gmail requires all senders to authenticate with either SPF or DKIM. Authentication results: DKIM = did not pass. SPF example.com with ip: x.x.x.x = did not pass

Technical meaning

In the accepted Gmail response, the temporary condition is triggered when its authentication results show both DKIM and SPF did not pass. The response identifies Gmail-specific rate limiting for that attempt; it does not claim that every authentication failure at every receiver behaves the same way.

Delivery status

The leading 4 identifies a temporary class in the enhanced status code. The accepted capture must be kept in its exact form; validate the basic SMTP reply class separately from the live transaction before using it as an operational property. The condition may clear after verified authentication remediation and appropriate pacing.

Class
Temporary failure
Retry
Controlled retry
Suppression
Check the full context

Retry decision

Keep the raw reply and authentication results, verify the SPF and DKIM configuration actually used by the message, correct only confirmed defects, then use backoff, jitter, idempotency, a reduced pace, and an attempt limit. Stop repeating unchanged sends while both mechanisms fail.

Suppression decision

Do not suppress recipients from 4.7.26 alone. The accepted condition concerns sender authentication and rate behavior, not a recipient mailbox; use independent recipient-level permanent evidence for suppression.

Common causes

  • The message's SPF and DKIM authentication paths both fail in the accepted Gmail diagnostic.
  • A DNS, signing, alignment, or sending-service change changed the authentication result for the traffic.
  • Traffic continues at a pace that does not respect Gmail's temporary backpressure.

Diagnostic steps

  1. Confirm the exact raw Gmail capture and its authentication-result details; validate the basic SMTP reply class separately from the transaction record.
  2. Correlate the failed attempt with the From domain, envelope sender, DKIM signing domain, sending IP, and current DNS records.
  3. Check SPF evaluation and DKIM signature results in the sending system without treating an assumed configuration as proof.
  4. Correct verified authentication defects, reduce send pace, and run bounded retries.

Actions by owner

Sender

  • Stop repeated manual resend attempts and provide the full response, sending domain, and time to the sender administrator.

Sender administrator

  • Verify SPF and DKIM for the actual sending path, correct confirmed defects, and pace recovery by affected traffic.

Provider

  • Inspect signing, DNS, and sending-IP context, then apply rate control while the authentication issue is remediated.

Sources

These sources define what this enhanced status code means, mainly through the IANA registry and related RFCs. When provider examples appear on the page, they come from that provider's published documentation. Follow the links to read the original wording in context.

Last verified:

Found an error or inaccuracy? Report a correction.

Point out the part of this page that should be checked. Every report is reviewed manually.

Type of problem

Describe the issue and, if useful, suggest corrected wording.

For a factual report, include a public source when possible.

You can submit anonymously. A reply is not guaranteed.

Do not paste full bounce messages, headers, email addresses, Message-IDs, tokens, or other personal data. Redact evidence before sending.

Sending a correction shares the information you enter with Formspree so I can review and improve this page. Read the privacy notice.

Guide

  • Deliverability

    Verify SPF and DKIM on the real sending path before resuming volume.

  • Sending Reliability

    Stay under Gmail's rate limit while the authentication fix lands.

  • Deliverability

    SPF/DKIM/DMARC and related auth policy are required for inbox delivery.

Incidents

Wojtek Blazalek

Email deliverability expert

Stuck on this error code? I help teams identify rejection causes and fix authentication and reputation, so email reaches the inbox.

Hands-on deliverability work for teams that send at scale.