How does Google Postmaster compliance work and what are the volume thresholds for bulk senders?
Published 15 May 2025
Updated 7 Oct 2026
13 min read
Summarize with
Updated on 11 Oct 2026: We clarified Gmail's bulk sender thresholds, Postmaster data availability, and the checks needed for authentication and one-click unsubscribe.
Google Postmaster compliance works by checking whether mail sent to personal Gmail accounts meets Gmail's sender requirements. The bulk sender threshold is close to 5,000 messages in a 24-hour period, counted across the same primary domain. Once a domain reaches that threshold, Google treats it as a bulk sender permanently.
Prepare for the bulk sender requirements before volume approaches 5,000 messages to personal Gmail accounts per day. Google can show compliance signals to lower-volume domains, dashboard data can lag, and one volume spike can change the domain's status.
- Close to 5,000 messages in 24 hours to personal Gmail accounts is the bulk sender line.
- Google counts mail by primary domain, so mail from subdomains rolls up to the same domain.
- Bulk sender status has no expiration date after Google assigns it.
- Keep spam complaints below 0.10% and avoid ever reaching 0.30%.
Google's bulk sender threshold
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 sender guidance uses these user-reported spam rate bands.
Recommended target
Below 0.10%
Stay below Google's recommended spam-rate threshold.
Warning range
0.10% to below 0.30%
Investigate complaints before increasing volume.
Policy violation
0.30% or higher
Violates the spam-rate requirement; inbox 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 0.10% already hurt inbox delivery for bulk senders. Rates above 0.30% make bulk senders ineligible for mitigation, which is Google's delivery support. Spam-related mitigation eligibility returns after the rate stays below 0.30% for 7 consecutive days, provided all other sender requirements are met. This does not guarantee inbox recovery. Google explains these rules in its sender guidelines FAQ.
Below bulk threshold
- SPF or DKIM, valid forward and reverse DNS, TLS, RFC 5322 formatting, and spam rates below 0.30% are required.
- Postmaster data can be sparse when Gmail volume is low.
- Build the stronger bulk sender setup before volume grows.
Bulk sender
- SPF and DKIM must authenticate, and direct mail must pass DMARC through at least one matching authenticated domain.
- Marketing and subscribed messages need one-click unsubscribe and removal within 48 hours; transactional messages are excluded.
- Once assigned, bulk sender status is permanent.
What the compliance dashboard checks
Google Postmaster Tools Compliance status dashboard showing Compliant, Needs work, and No data found.
The Compliance status dashboard is available to all senders that send to personal Gmail accounts, including senders below the bulk threshold. It reports three states: Compliant, Needs work, and No data found. Treat No data found as a measurement gap, not proof that the domain is clean.
|
|
|
|
|---|---|---|---|
SPF and DKIM status | All senders; both for bulk | At least one passes; bulk mail passes both | Fix DNS and signing |
DNS records | All senders | Forward and matching reverse DNS | Repair PTR and hostnames |
Message format | All senders | RFC 5322 headers and Message-ID | Correct malformed headers |
Encryption | All senders | TLS on delivery | Check SMTP TLS |
Spam rate | All senders | User-reported spam rate below 0.30% | Reduce unwanted mail |
DMARC | Bulk senders | DMARC policy and a passing SPF or DKIM domain that matches From | Publish and monitor policy |
One-click unsubscribe | Bulk marketing | RFC 8058 headers and HTTPS endpoint | Fix headers and POST handling |
Honor unsubscribe | Bulk marketing | Removal within 48 hours | Trace removal jobs |
Compliance areas shown in Google Postmaster Tools
Dashboard data usually updates within 24 hours, but a resolved issue can take up to 7 days to change status because compliance uses a rolling average over multiple days. A same-day DNS fix can be correct now and still show Needs work until Google receives enough matching mail and recalculates the status. See Google's dashboard documentation for the status definitions and reporting delays.
Postmaster Tools v2 also includes Deliverability analysis under Compliance status. It gives domain-level recommendations when sending volume is too low, messages fail to deliver, spam exceeds the recommended threshold, recipient interaction signals are weak, recipients indicate they want more mail, or sender requirements are missed. Use it for triage, then confirm the cause in authentication data and SMTP logs.
How Gmail enforces non-compliance
Google began ramping up enforcement against non-compliant traffic in November 2025. That enforcement is active: authentication, DNS, TLS, message format, or From-domain matching failures can trigger temporary rate limits, permanent rejections, or spam placement. Missing DMARC, missing one-click unsubscribe, slow unsubscribe processing, and spam rates above 0.30% also remove eligibility for delivery mitigation.
|
|
|
|---|---|---|
PTR or matching forward DNS fails | Rate limit or rejection | 4.7.23 or 5.7.25 |
SPF fails | Rate limit or rejection | 4.7.27 or 5.7.27 |
TLS is missing | Rate limit or rejection | 4.7.29 or 5.7.29 |
DKIM fails | Rate limit or rejection | 4.7.30 or 5.7.30 |
DMARC record or policy is missing | Rate limit and no mitigation | 4.7.31 |
From domain does not match SPF or DKIM | Rate limit, rejection, or spam placement | 4.7.32 |
Representative Gmail sender-requirement errors
Treat a 4.x response as a temporary failure: reduce the affected sending rate, investigate the reason, and let the sending server retry with backoff. A 5.x response is a permanent failure for that delivery attempt; for the configuration errors listed above, fix the stated cause before resending. Log enhanced status codes by sending domain and message stream because the SMTP response often identifies the cause before the rolling compliance dashboard changes.
Passing every compliance row does not guarantee inbox placement. Compliance is the eligibility baseline. Gmail also evaluates sender reputation, recipient feedback, sending patterns, message content, and IP behavior.
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 this sender-guideline threshold, even though those mailboxes also use Google infrastructure. Count messages across your sending systems, including transactional mail as well as marketing mail. The threshold determines bulk sender classification; it is not a daily sending allowance.
Gmail's 24-hour bulk sender count across a primary domain and its subdomains.
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. A mixed sending program can cross the threshold even when no single subdomain sends 5,000 messages.
- Personal Gmail and googlemail.com recipients count toward the threshold.
- Google Workspace recipients are outside this specific Gmail sender-guideline count.
- Subdomains count toward the same primary domain for bulk sender status.
- Lowering volume later does not remove bulk sender classification.
Postmaster Tools v2 is useful even when some charts are sparse. Its Compliance status and Deliverability analysis can guide troubleshooting when data is available. API v2 supports compliance checks, batch statistics queries across domains, and automated domain and user management. The related Postmaster Tools v2 guide explains access and data availability.
How to verify your domain and get Postmaster data
The bulk sender threshold and the volume needed to display dashboard data are different. Google's documentation does not specify a fixed daily message count that guarantees visible data. Low-volume days are filtered for privacy, so crossing 5,000 messages does not guarantee every chart will populate.
- Sign in with a Google Account and add the domain used for DKIM signing (d=) or SPF authentication (Return-Path).
- Publish the TXT or CNAME verification record supplied by Postmaster Tools, then complete domain verification.
- Select the verified domain and review Compliance status. Add sending subdomains separately for their other dashboard data; web compliance still reports the primary domain.
- If data is missing, check authentication on a received Gmail message and confirm that your traffic reaches personal Gmail accounts. Some dashboards require DKIM-authenticated mail.
Postmaster reports dates in UTC, so compare charts with sending logs in UTC. Keep sending to opted-in recipients at a steady rate; do not inflate volume just to fill charts. Google's setup instructions explain domain selection and verification.
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.
- The dashboard can lag current DNS, current headers, and current spam rate.
- Compliance status uses a different dataset than other Postmaster dashboards.
- The web Compliance status dashboard reports the primary domain, so a clean subdomain chart does not establish primary-domain compliance.
- Some days lack enough eligible mail for Google to expose full dashboard data.
Spam-rate interpretation also needs care. Postmaster's Spam Rate dashboard reports the share of eligible, DKIM-authenticated messages delivered to engaged recipients' inboxes that recipients mark as spam. This is not complaints divided by every attempted send. A 0.00% 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 can report them. That can make the user-reported rate look clean while reputation is still weak. Google explains this in its Spam Rate dashboard guidance.
Technical setup that passes the checks
Bulk senders need both 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. DKIM keys must be at least 1,024 bits; Google recommends 2,048 bits when the provider supports that length.
DMARC TXT record at _dmarc.example.com for Gmail bulk sender complianceDNS
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com
Google accepts p=none for the minimum bulk sender policy requirement, but messages must still pass DMARC. Use aggregate reports to identify legitimate senders and correct authentication failures before moving toward quarantine or reject. Relaxed domain matching is the default: the From domain must share its organizational domain with a passing SPF Return-Path domain or DKIM signing domain. Use adkim=s or aspf=s only when the relevant sending sources support an exact domain match.
One-click unsubscribe headersHTTP
List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: <HTTPS_UNSUBSCRIBE_URL>
The HTTPS endpoint must accept the RFC 8058 POST request with List-Unsubscribe=One-Click in the request body and remove the recipient from the associated mailing list within 48 hours. It must complete the request without login or another confirmation step. Cover both List-Unsubscribe headers with a valid DKIM signature. Marketing and subscribed messages also need a clearly visible unsubscribe link in the message body. A footer preference-center link does not replace the one-click headers.
Check that your firewall, CDN, and endpoint allow these requests: Google counts unsubscribe requests even when infrastructure blocks them before they reach your server. Correct headers also do not guarantee Gmail will display an unsubscribe button beside the sender; that display has separate eligibility checks.
?
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 Suped's domain health checker. For message inspection, send a real campaign sample through Suped's email tester so headers, authentication results, and unsubscribe headers are checked as received.
For ongoing source cleanup, use Suped's DMARC monitoring. DNS can look correct while a marketing platform or billing system still sends mail that fails SPF, DKIM, or DMARC.
How to diagnose and fix compliance issues
Issue steps to fix dialog showing the issue overview, tailored fix steps, and verification action
The Postmaster compliance dashboard shows Google's assessment of the domain. It does not always identify which sending source or message stream caused the problem. Use DMARC reports to investigate authentication failures, and SMTP logs or unsubscribe processing logs to investigate delivery and removal failures.
Suped is our DMARC and email authentication platform. When a Google authentication row says Needs work, use Suped's aggregate reports and authentication alerts to identify failing sources, then follow the issue-specific remediation steps for the required DNS or sender change.
- Review authentication failures and unverified sources to identify the sending system that needs attention.
- Follow issue-specific remediation steps and record who owns each DNS or sender change.
- Use Suped's multi-tenant dashboard to review authentication issues across client domains.
- Use Suped's blocklist monitoring for domain and IP blocklist (blacklist) visibility alongside authentication diagnostics.
Use weekly reviews for stable domains and daily reviews during infrastructure changes or Gmail deferrals. Confirm fixes with a fresh message and SMTP logs, then allow the compliance reporting window to catch up. For large domain portfolios, Google's API v2 compliance endpoint supports automated checks. Unlike the web dashboard, it can also return a separate subdomain compliance result when data is available.
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 unwanted 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 subdomain charts and missing the web compliance dashboard's primary-domain rollup.
Expecting a same-day status change when compliance uses a rolling average over several days.
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 view
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 view
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
Practical compliance checklist
Check every sending stream for passing SPF and DKIM, a valid DMARC policy, and a matching From domain. Confirm valid forward and reverse DNS, TLS, and RFC 5322 formatting. For marketing and subscribed mail, test one-click unsubscribe and the visible body link, and verify removal within 48 hours. Keep the user-reported spam rate below 0.10%. If the dashboard says Needs work, fix the cause and validate a fresh message before waiting for the reporting window to catch up.
