Gmail bulk sender compliance
Check Gmail bulk sender requirements
Gmail bulk senders need more than SPF, DKIM and DMARC records that merely exist. The real question is whether the messages authenticate, align, use compliant infrastructure and give subscribed recipients an easy way to leave.
A domain sends close to 5,000 or more messages per day to personal Gmail recipients and needs a path-specific compliance result.
Gmail bulk sender compliance SPF PASS DKIM PASS DMARC FAIL PTR / FCrDNS UNKNOWN One-click unsub UNKNOWN Spam rate UNKNOWN
Open the Gmail bulk sender check
When Gmail's bulk sender rules apply
Google describes a bulk sender as one that sends close to or above 5,000 messages to personal Gmail accounts within 24 hours. Volume from the same primary domain and its subdomains is counted together. Once Google classifies a sender as bulk, that classification does not expire simply because later volume falls.
The extended form should ask for approximate daily Gmail volume and explicit confirmation of bulk-sender status. It must not infer a non-bulk result from DNS.
Gmail bulk requirements and test contract
| Requirement | Evidence needed | How to evaluate it | Important boundary |
|---|---|---|---|
| SPF authentication | Sender IP and envelope MAIL FROM domain; receiver-reported spf= result when available. | Evaluate the selected SPF record for the entered IP and envelope identity. Preserve DNS and receiver evidence separately. | An SPF record at the visible From domain does not prove the message passed SPF. |
| DKIM authentication | Selector, signing domain, public key and receiver-reported dkim= result. | Validate DNS key structure; use trusted message evidence for the message-level pass. | A public key cannot prove the sender actually signed the message. |
| DMARC record and alignment | Visible From domain; effective DMARC record; authenticated SPF and DKIM domains. | Require a DMARC record with at least p=none. For direct mail, require aligned SPF or aligned DKIM to pass DMARC. | Record presence is not message-level DMARC success. Indirect forwarded/list mail has different alignment handling. |
| PTR and forward DNS | Every actual sending IP supplied or observed. | Resolve IP to PTR and each PTR hostname to A/AAAA; require the original IP in the forward answer. | Do not enumerate SPF CIDRs or certify an entire provider include from one IP. |
| TLS | Receiver-observed headers or transport evidence. | Report receiver evidence when available; otherwise return UNKNOWN. | Public DNS alone cannot prove that a specific message used TLS. |
| Message format | Representative complete headers and rejection details. | Surface specific RFC 5322 defects that are actually observable. | A domain-only check must not claim full format compliance. |
| Spam rate | Google Postmaster Tools spam-rate data. | Show the provided value and date. Target below 0.1%; never allow it to reach 0.3% or higher. | DNS and a single message cannot measure recipient complaints. |
| One-click unsubscribe | Marketing/subscribed classification, complete relevant headers and body confirmation. | Check RFC 8058 List-Unsubscribe-Post, an HTTPS unsubscribe URL and confirmation of a visible body link. | Applies to marketing and subscribed bulk mail, not every transactional message. |
Minimum evidence for a useful bulk-sender result
- Visible From domain for DMARC policy discovery and alignment.
- Envelope MAIL FROM domain and actual sender IP for SPF and FCrDNS.
- DKIM selector and signing domain, preferably from a representative delivered or rejected message.
- Message headers for receiver-reported authentication, transport, unsubscribe headers and the identities receivers evaluated.
- Approximate daily volume to personal Gmail and whether Google already identifies the domain as a bulk sender.
- Message type: transactional, marketing/subscribed or mixed.
- Google Postmaster Tools observations, including spam rate and compliance warnings, entered with an observation date.
DMARC PASS is not the same as a DMARC record
The visible From domain determines the DMARC policy domain. A message passes DMARC when at least one authenticated path aligns with it: either the SPF-authenticated MAIL FROM domain or the DKIM-authenticated signing domain. A syntactically valid p=none record satisfies the minimum policy-publication requirement, but it does not make an unaligned message pass.
The compliance result should therefore show separate rows for DMARC policy configured, SPF alignment, DKIM alignment and receiver-reported DMARC.
PTR coverage must follow real sender IPs
Check an explicitly entered IPv4 or IPv6 address and exact sender addresses safely derived from trusted evidence. Each address needs a meaningful PTR hostname whose A or AAAA lookup returns the original IP. Large ip4/ip6 ranges and third-party SPF includes are authorization descriptions, not a finite list of active senders; the UI should request the actual IP instead of expanding them.
Compliance result states
DMARC FAIL
Explain whether the failure is a missing policy, an SPF alignment failure, a DKIM alignment failure or a receiver-reported result. Never reduce all four to "add DMARC."
One-click unsubscribe UNKNOWN
Request relevant message headers and message type. Do not fail transactional mail solely because marketing unsubscribe evidence was not supplied.
PTR PASS
List the checked sender IP, PTR hostname and matching forward address so the user can reproduce the result.
Spam rate UNKNOWN
Direct the user to Google Postmaster Tools. A green DNS result cannot substitute for reputation data.
Prioritize a safe correction
- Fix hard authentication failures for the exact sender path: SPF, DKIM and then DMARC alignment.
- Correct missing or mismatched FCrDNS through the owner of each actual sending IP.
- Enable TLS and repair message-format errors in the sending platform.
- For marketing or subscribed mail, add RFC 8058 one-click unsubscribe and a visible unsubscribe link, then honor requests promptly.
- Review Google Postmaster Tools after new traffic arrives; DNS changes alone cannot correct complaints or unwanted-mail behavior.
Test the identities Gmail actually evaluates
Use the sending IP, envelope domain, visible From domain, DKIM identity and representative message evidence. Missing evidence should produce a precise request, not a misleading pass.
Frequently asked questions
Who does Google classify as a bulk sender?
Google treats a sender that approaches or exceeds 5,000 messages to personal Gmail accounts in a 24-hour period as a bulk sender. Messages from the same primary domain and its subdomains are counted together, and the classification is permanent.
Does Gmail require a rejecting DMARC policy?
No. Google requires a DMARC record for bulk senders and accepts p=none as the minimum policy, but direct mail still needs alignment through SPF or DKIM.
Is List-Unsubscribe enough for Gmail marketing mail?
No. Marketing and subscribed bulk mail needs RFC 8058 one-click unsubscribe headers and a clearly visible unsubscribe link in the message body.
Related email diagnostics
Primary sources: Google Email sender guidelines, Google Email sender guidelines FAQ, Google Postmaster sender requirements FAQ, RFC 8058 one-click unsubscribe.