How does Google Postmaster compliance work and what are the volume thresholds for bulk senders?
Matthew Whittaker
Co-founder & CTO, Suped
Published 15 May 2025
Updated 25 May 2026
9 min read
Summarize with
Google Postmaster compliance works by checking whether mail sent to personal Gmail accounts meets Gmail's sender requirements. The main bulk sender threshold is close to 5,000 messages or more to personal Gmail accounts within a 24-hour period, counted across the same primary domain. Once a domain hits that threshold, Google treats it as a bulk sender permanently.
The practical answer is simple: do not wait until you are comfortably above 5,000 Gmail recipients per day. I treat the bulk sender requirements as the baseline for any serious sender because Google can show compliance signals to lower-volume domains, dashboard data can lag, and a one-time volume spike can change the domain's status.
- Threshold Close to 5,000 messages in 24 hours to personal Gmail accounts is the bulk sender line.
- Counting Google counts mail by primary domain, so mail from subdomains rolls up to the same domain.
- Status Bulk sender status has no expiration date after Google assigns it.
- Target Keep spam complaints below 0.10% and avoid ever reaching 0.30%.
The direct answer
Google's bulk sender threshold applies when a sender sends close to 5,000 messages or more to personal Gmail accounts, such as addresses ending in gmail.com or googlemail.com, within a 24-hour period. Google counts those messages by primary domain. If example.com sends 2,500 messages and news.example.com sends 2,500 messages to personal Gmail accounts on the same day, Google treats that as 5,000 messages from example.com.
Spam complaint thresholds
Google's compliance and deliverability guidance uses these user-reported spam rate bands.
Healthy target
Below 0.10%
Keep complaint rates here for normal sending resilience.
Risk band
0.10%-0.29%
Investigate list quality, cadence, and message fit quickly.
Maximum breach
0.30%+
At this point, Google can deny mitigation and delivery can suffer.
The compliance dashboard does not act like a live DNS checker. It uses received mail, rolling data, and Gmail's own filters. That is why a domain can look fine in one dashboard and still show Needs work in the compliance view. For the underlying policy text, Google's own sender guidelines are the reference point.
For spam rate, 0.30% is not the point where every message instantly fails. It is the policy ceiling. Google says rates above that make bulk senders ineligible for mitigation, and eligibility returns after the rate stays below 0.30% for 7 consecutive days. Delivery impact is graduated, so the operating target stays under 0.10%.
Below bulk threshold
- Baseline SPF or DKIM, valid DNS, TLS, RFC 5322 formatting, and low spam rates still matter.
- Visibility Postmaster data can be sparse when Gmail volume is low.
- Advice Build the stronger bulk sender setup before volume grows.
Bulk sender
- Authentication SPF, DKIM, and DMARC must be in place.
- Unsubscribe Marketing and promotional mail needs one-click unsubscribe and 48-hour processing.
- Duration Once assigned, bulk sender status is permanent.
What the compliance dashboard checks
Google Postmaster Tools compliance dashboard with sender requirement statuses.
The Compliance status dashboard is available to senders that send to personal Gmail accounts. It reports three main states: Compliant, Needs work, and No data found. I read No data found as a measurement problem, not proof that the domain is clean.
|
|
|
|
|---|---|---|---|
SPF and DKIM | All senders | Mail authenticates | Fix DNS and signing |
DNS records | All senders | Forward and reverse DNS | Repair PTR and hostnames |
Encryption | All senders | TLS on delivery | Check SMTP TLS |
Spam rate | All senders | User reports | Reduce unwanted mail |
DMARC | Bulk senders | Record and domain match | Publish policy |
Unsubscribe | Bulk marketing | Headers and processing | Honor within 48 hours |
Compliance areas shown in Google Postmaster Tools
The dashboard can take up to 7 days to reflect a fix because it uses a rolling data average over multiple days. A same-day DNS change can be correct now and still show Needs work until Google has enough matching mail and enough time to recalculate.
Enforcement differs by issue. Authentication, DNS, TLS, formatting, and From-domain match failures can lead to temporary failures, permanent failures, or spam foldering. Spam rate breaches, missing DMARC, missing one-click unsubscribe, and slow unsubscribe processing can make the sender ineligible for delivery mitigation.
How Google counts volume
The 5,000-message threshold is not a total internet send count. It is mail to personal Gmail accounts in a 24-hour period. Mail to Google Workspace accounts does not count for the sender guideline threshold, even though those mailboxes also use Google infrastructure.
Flowchart showing how Gmail bulk sender volume is counted.
The primary-domain rule matters. Splitting campaigns across mail.example.com, news.example.com, and offers.example.com does not avoid the count if all of that mail rolls up under example.com. It also means a mixed sending program can cross the threshold even when no single subdomain sends 5,000 messages.
- Included Personal Gmail and googlemail.com recipients count toward the threshold.
- Excluded Google Workspace recipients are outside this specific Gmail sender guideline count.
- Aggregated Subdomains count toward the same primary domain for bulk sender status.
- Permanent Lowering volume later does not remove bulk sender classification.
Low-volume senders still need context because Postmaster Tools can show some compliance information before every other dashboard has stable data. That is why the Postmaster Tools v2 interface is useful even when volume is not high enough to populate every chart.
Why compliance can look inconsistent
The most confusing cases are domains with a spam rate under 0.30% that still show non-compliant, or domains over 0.30% that do not immediately show the expected status. The dashboard is not a single spam-rate gauge. It checks multiple requirements, multiple days of mail, and primary-domain rollups.
- Rolling data The dashboard can lag current DNS, current headers, and current spam rate.
- Different data Compliance status uses a different dataset than other Postmaster dashboards.
- Primary domain A clean subdomain view does not mean the primary domain status is clean.
- Low volume Some days lack enough eligible mail for Google to expose full dashboard data.
Spam-rate interpretation also needs care. A 0.00% user-reported spam rate does not automatically mean inbox placement is healthy. If Gmail is already placing many messages in spam, fewer recipients see them in the inbox and fewer recipients can mark them as spam. That can make the user-reported rate look clean while reputation is still weak.
Technical setup that passes the checks
The technical checklist is straightforward, but the operating details matter. Bulk senders need SPF and DKIM authentication, a DMARC record for the sending domain, a From domain that matches either the SPF or DKIM organizational domain for direct mail, valid forward and reverse DNS, TLS, standards-compliant headers, low complaint rates, and proper unsubscribe handling for promotional mail.
Minimum DMARC record for Gmail bulk sender complianceDNS
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com; ri=86400; pct=100; adkim=s; aspf=s
A policy of p=none is enough for Google's minimum bulk sender DMARC requirement, but it is not a long-term protection strategy. I prefer starting there only while reports confirm all legitimate senders, then moving toward quarantine or reject once the authentication sources are clean.
One-click unsubscribe headersHTTP
List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: <HTTPS_UNSUBSCRIBE_URL>
The unsubscribe endpoint needs to accept the POST request and remove the recipient within 48 hours. Do not rely on a footer preference-center link alone for the one-click requirement. The visible footer link is still useful for humans, but the header is the compliance mechanism.
?
What's your domain score?
Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.
Before interpreting Postmaster data, check the domain's current DNS and authentication state with a domain health checker. For live message inspection, send a real campaign sample through an email tester so headers, authentication results, and unsubscribe headers are checked as received.
For ongoing work, DMARC monitoring is where the real cleanup happens. DNS can look correct while a marketing platform, CRM, billing system, or support desk is still sending mail that fails SPF, DKIM, or DMARC.
How I operationalize compliance
Issue steps to fix dialog showing the issue overview, tailored fix steps, and verification action
The Postmaster compliance dashboard tells you what Google currently believes about the domain. It does not always tell you which vendor, selector, DNS record, source IP, or message stream caused the problem. That is the gap Suped is built to close.
For most teams, Suped is the strongest practical DMARC platform because it connects the compliance work into one workflow: DMARC, SPF, DKIM, hosted SPF, hosted DMARC, blocklist monitoring, alerts, and issue-specific steps to fix. That matters when a Google row says Needs work and the team needs to know what changed, who owns it, and what DNS or sender action fixes it.
- Detection Suped flags authentication failures, unverified sources, policy gaps, and sender drift.
- Fixes Each issue has practical steps instead of raw XML report digging.
- Scale The MSP and multi-tenant dashboard helps agencies manage many domains without spreadsheet tracking.
- Reputation Suped pairs DMARC work with blocklist monitoring for domain and IP blocklist (blacklist) visibility.
The operating rhythm I use is weekly for stable domains and daily during infrastructure changes, sender migrations, high-volume campaigns, or any period where Gmail deferrals appear. Postmaster tells you how Gmail is judging the domain. Suped gives the domain owner the evidence and workflow needed to fix the underlying authentication and reputation issues.
Views from the trenches
Best practices
Treat 5,000 as an operational trigger, not a ceiling you can safely brush against daily.
Track compliance by primary domain because subdomain mail still rolls up into one status.
Keep complaint rates below 0.10% so one bad campaign does not push you toward 0.30%.
Test unsubscribe handling with real POST requests and confirm removals finish within 48 hours.
Common pitfalls
Assuming low Postmaster spam rate means inboxing is healthy when mail is already in spam.
Checking only subdomains and missing that compliance reports on the primary domain.
Waiting for the dashboard to update in one day when compliance can need a 7 day window.
Treating one-click unsubscribe as a visible footer link instead of proper RFC 8058 headers.
Expert tips
Use Feedback-ID values consistently so campaign-level complaint signals can be diagnosed.
Separate transactional and marketing streams so unsubscribe rules fit the message type cleanly.
Monitor DMARC sources daily after infrastructure changes, not only after Gmail defers mail.
Keep DNS fixes documented with owner, date, and expected Postmaster status change window.
Expert from Email Geeks says compliance status can be confusing because a domain below 0.30% can still fail when another requirement or data window is failing.
2024-05-21 - Email Geeks
Marketer from Email Geeks says lower-volume B2C senders can see warning signals before crossing 5,000 daily Gmail messages, so they treat the rules as the baseline.
2024-05-21 - Email Geeks
My practical recommendation
Treat Google Postmaster compliance as an operational health check, not a one-time setup task. The threshold answer is close to 5,000 messages to personal Gmail accounts in 24 hours, counted by primary domain, with permanent bulk sender status after assignment. The compliance answer is broader: authenticate correctly, keep complaint rates low, process unsubscribe requests within 48 hours, and check the dashboard after enough fresh mail has passed through Gmail.
The safest posture is to meet the bulk sender requirements before Google forces the issue. That means SPF and DKIM working, DMARC published and monitored, the From domain matching an authenticated organizational domain, TLS on delivery, clean DNS, proper unsubscribe headers, and a complaint-rate target under 0.10%. If the compliance dashboard says Needs work, fix the technical cause first, then allow the rolling data window to catch up.
