Gmail’s November 2025 enforcement ramp: sender rules and Postmaster Tools now

The latest dated status is an enforcement ramp, not a new rule

Google’s current Email sender guidelines FAQ says that Gmail started ramping up enforcement on non-compliant traffic in November 2025. The same notice warns that messages failing the requirements can face disruptions, including temporary and permanent rejections. As of 29 October 2026, this is the newest explicit date tied to sender enforcement in the official pages reviewed here. ^[1]

That date does not mean Google has published a one-day switchover or an end date. The FAQ says enforcement is ramping up, but it does not provide a public phase-by-phase calendar, a date by which every non-compliant message will be rejected, or a universal deadline for senders to complete remediation. Do not treat the November 2025 marker as the start of a grace period that is still open. ^[1]

Google introduced the core bulk-sender requirements in 2023 for implementation from February 2024. The current guide is now titled Email sender guidelines, and its FAQ says it was formerly called Bulk sender guidelines. The enforcement ramp adds consequences to the existing framework; it does not announce a different authentication standard. ^{[1] [3]}

Who is covered, and what is mandatory

These rules cover mail sent to personal Gmail accounts, meaning addresses on gmail.com and googlemail.com. Google defines a bulk sender as one that sends 5,000 or more messages in a day to Gmail accounts. That is the published volume threshold for the bulk-sender rules; it does not remove the baseline requirements that apply to all senders. ^{[1] [2]}

For all senders, Google’s minimum authentication requirement is SPF or DKIM. Bulk senders must set up SPF, DKIM and DMARC. Google also requires the sending IP to have a PTR record whose hostname resolves back to that same IP. These are technical basics to verify across every platform, sending domain and IP that sends to Gmail recipients. ^[2]

DMARC must be more than a record that exists in DNS: Google explains that a message passes DMARC when SPF or DKIM authenticates it and the authenticating domain matches the domain in the visible From field. Google recommends using SPF, DKIM and DMARC even below the bulk threshold, but that recommendation is distinct from the stated minimum for all senders. ^[2]

Unsubscribe rules and spam-rate guidance

Bulk senders must support one-click unsubscribe for marketing and subscribed messages. Google’s guidance does not require one-click unsubscribe on every transactional message. Google’s setup instructions specify the List-Unsubscribe and List-Unsubscribe-Post headers, and its original announcement said senders must process requests within two days. Keep the headers and actual opt-out handling aligned. ^{[2] [3]}

Google’s published spam-rate guidance is to keep the reported rate below 0.10% and avoid reaching 0.30% or higher. Treat these as operational limits to monitor closely, not as a publicly documented single rejection trigger: the current pages do not publish a universal formula that maps an individual rate to a specific delivery outcome. Lower complaint levels also depend on sending wanted mail and honoring opt-outs. ^[2]

A separate Gmail product update arrived on 8 July 2025: Gmail introduced a Manage subscriptions view where recipients can review frequent senders and unsubscribe in one place. Gmail sends that unsubscribe request to the sender. Google’s announcement points bulk senders back to the existing guidelines; it does not describe a new technical requirement or a new response deadline. ^[8]

What enforcement means in practice

The current official wording is that non-compliant traffic may face temporary or permanent rejections as enforcement ramps up. Google’s FAQ includes a section on the error codes Gmail returns, and the exact response for your own traffic is the best starting point. Read that SMTP response, then check authentication, DNS, unsubscribe handling and complaint trends before resuming a failed stream. ^[1]

The sender guide also describes rate limits, spam classification and rejection as possible Gmail responses to sending problems. They are not evidence that a message will reach the inbox once a technical check passes. Authentication and list hygiene are prerequisites for a sound program, not a promise about placement. Watch real delivery results by message type and reduce volume if deferrals or bounces rise. ^[2]

Postmaster Tools v2: what changed and what remains unclear

Google’s current Postmaster Tools help describes v2 as the newer interface and identifies a Compliance status dashboard that helps senders monitor adherence to the sender guidelines. A companion Google FAQ lists diagnostic areas for SPF and DKIM, DMARC, message format, DNS records, encryption, user-reported spam and unsubscribe issues. This is a compliance view of sending signals, not a new inbox-placement score. ^{[4] [7]}

The legacy-interface status is less final than some old migration notices suggest. Google’s current deprecation help says it postponed deprecation after sender feedback, encourages transition to v2 and says v1 will eventually be retired. It says Google will share more details later, but the page gives no replacement retirement date. ^[4]

Google’s live dashboard catalog currently lists Compliance status, Spam Rate, IP Reputation, Domain Reputation, Feedback Loop, Authentication, Encryption and Delivery Errors. If your team relies on the reputation views, check what your own account shows, because Google says the older interface will eventually be retired. ^{[4] [5]}

Use the data carefully and check the basics first

Postmaster Tools data applies to mail sent to personal Gmail accounts, not every mailbox provider or every Google Workspace recipient. Google says dashboard data is not real time; it is typically updated within 24 hours but can take longer. Some dashboards may omit low-volume days to protect user privacy, so an empty chart is not proof that a domain has no delivery issues. ^{[5] [6]}

To use the tool, add and verify the domain used for SPF or DKIM authentication. Google’s setup guide notes that low daily volume can leave dashboards without data. Check DNS and authentication records directly as well as the dashboards, and compare the dashboard’s reporting window with the dates of any sending change before drawing conclusions. ^{[5] [6]}