For a long time, many teams treated Gmail's 4.7.x bulk-sender errors like a warning light that could stay on for a while.
That was already risky. After Google's November 2025 enforcement escalation, it became a worse assumption.
Google's current Email sender guidelines FAQ now says that Gmail is ramping up enforcement on non-compliant traffic and that messages which fail the sender requirements will experience disruptions, including temporary and permanent rejections. That is the important shift to internalize: a deferral is no longer something to read as a soft, indefinite grace period.
If the baseline requirements need a refresher first, Gmail, Yahoo, and Microsoft email sender requirements, Gmail bulk sender status explained, and Gmail bulk sender error codes explained are the nearby references. This post is about the enforcement escalation itself.
For Gmail bulk senders, the practical read in 2026 is:
4.7.x means Gmail is still deferring or rate limiting the traffic5.7.x class means Gmail has moved to a hard block for that requirement failure4.7.x responses as something they can live with for days or weeksIn plain terms: temporary failures are now part of the same enforcement ladder as permanent failures.
Google did not publish a brand-new sender checklist in November 2025.
The requirements were already familiar:
p=none5322-conformant messagesWhat changed is the enforcement framing.
Google's FAQ now says non-compliant traffic will experience disruptions including temporary and permanent rejections. That matters because many operations teams used to interpret bulk-sender failures this way:
4.7.x means slow down and retry.5.7.x means a serious compliance problem.That split is no longer safe. The safer mental model is:
4.7.x is Gmail telling you the sender requirement failure is already affecting live traffic.4.7.x states can be part of the path toward 5.7.x blocking.Google's FAQ is unusually direct here because it maps specific requirement failures to temporary or permanent failure handling.
The highest-risk classes are the familiar technical ones:
From: domain not aligned with SPF or DKIM under DMARC rules5322Those are not just reputation hints. They are sender-requirement violations that Google explicitly associates with rejection and spam-foldering outcomes.
The usual SMTP progression looks like this:
4.7.23 can appear when reverse DNS is not acceptable4.7.27 can appear when SPF does not pass4.7.30 can appear when DKIM does not pass4.7.31 or 4.7.40 can appear when DMARC publication is missing or unusable4.7.32 can appear when the visible From: domain is not alignedAnd then the harder side of the ladder appears in the 5.7.x family, such as 5.7.25, 5.7.27, 5.7.29, 5.7.30, 5.7.32, and 5.7.40, depending on the exact problem and which Google reference page you are reading.
That is why the right operational question is not "are we only seeing temporary errors?"
It is: which sender requirement is already failing in production, and how long has Gmail been having to tell us about it?
Not every Gmail requirement behaves the same way.
Google's FAQ separates some requirements into a different kind of consequence. For example:
0.3% make bulk senders ineligible for mitigation while the rate stays too high48 hours has the same mitigation-eligibility problemSo the November 2025 escalation should not be simplified into "every missing requirement now becomes an instant hard bounce."
That would be inaccurate.
The accurate reading is narrower and more useful:
Missing one-click unsubscribe is still a serious Gmail compliance problem. But Google's FAQ says the direct consequence is primarily higher spam risk and loss of mitigation eligibility, not an automatic hard reject on its own.
Most teams that get surprised here do not think of themselves as non-compliant.
They usually have some of the requirements in place. The real failure is that one live path is still broken:
From: domainThat is why Google's Postmaster Tools compliance dashboard matters so much now. It gives a domain-level view of whether Gmail is actually seeing the sender as compliant across SPF, DKIM, DMARC, DNS, formatting, encryption, spam behavior, and unsubscribe handling.
If that dashboard says Needs work, the right assumption is not "the paperwork is incomplete."
The right assumption is "Gmail is already observing something on live traffic that can influence enforcement."
4.7.x after November 2025The old low-discipline habit was to let 4.7.x sit in a retry queue and hope delivery would clear later.
That is now the wrong posture for bulk-sender compliance errors.
Treat 4.7.x like an active incident, especially when the response text points to a specific requirement such as SPF, DKIM, DMARC, alignment, PTR, or TLS.
The reason is simple:
In other words, the difference between 4.7.27 and 5.7.27 is not the difference between "fine" and "not fine."
It is the difference between already bad and now fully blocked.
When a bulk sender starts seeing 4.7.x requirement errors, this is the response sequence worth following:
Authentication-Results, From:, Return-Path, and DKIM-Signature rather than trusting only vendor dashboards.If the issue is specifically volume-sensitive, Google's Top 10 Gmail sender issues still says to ramp up slowly and keep sending volumes consistent. That guidance matters because unstable volume often exposes weak authentication or poor list quality faster than steady-state traffic does.
When several things look wrong at once, fix in this order:
5322That order is not because unsubscribe or complaints are unimportant. It is because the first group is most directly tied to the "temporary now, permanent later" enforcement path Google is spelling out.
The broader trend is not hard to read.
Google permanently classifies domains as bulk senders once they meet the threshold, and it already says new domains face accelerated enforcement progression. Put those together with the November 2025 escalation language and the message is clear:
Google expects bulk-sender compliance to be an operating condition, not something a sender restores only after mail starts failing.
That has two consequences for 2026 sender operations:
4.7.x compliance error should be handled as an early-stage rejection problem, not as harmless throttlingAfter November 2025, the safest way to read Gmail bulk-sender enforcement is this: temporary deferrals and permanent rejections are not separate worlds anymore.
They are part of the same progression.
If Gmail is already returning 4.7.x errors for SPF, DKIM, DMARC, alignment, PTR, TLS, or message-formatting problems, the sender should behave as if enforcement has already started, because it has. The only reliable way to stop that progression is to fix the underlying requirement quickly, validate the result on live mail, and keep checking Postmaster Tools before the issue graduates into a 5.7.x block.