If you send a lot of mail to Gmail (Google’s bulk bar is about 5,000 messages a day to Gmail users), you must prove the mail is really from you and keep spam complaints low. That means public DNS records (SPF, DKIM, DMARC — see the dotted words), reverse DNS on sending IPs, encrypted delivery (TLS), and one-click unsubscribe on marketing mail. Google wants spam reports near 0.1% and treats 0.3% as the cliff. Under 5,000 a day you still need basic authentication — you do not get a free pass.

In forceInboxIn force 1 Feb 2024Verified 2 Aug 2026

Gmail enforces authentication, PTR, TLS and a 0.30 percent spam rate

Q: What is Gmail's spam rate threshold for bulk senders?

Every sender to personal Gmail accounts needs at least SPF or DKIM, valid forward and reverse DNS (PTR) on sending IPs, TLS in transit, RFC 5322 formatting, and a user-reported spam rate under 0.30 percent in Postmaster Tools. Senders of about 5,000 or more messages a day to personal Gmail must use both SPF and DKIM, publish DMARC at least p=none, align the From domain, and support one-click unsubscribe for marketing mail. Google asks bulk senders to stay under 0.10 percent spam and treats 0.30 percent as the line you must never reach. Google's sender guidelines do not mention ARC at all: ARC is Apple's requirement and Yahoo's recommendation, not Gmail's.

Q: What happens if you do not?

Less silent than its reputation. Google's own guidelines publish the temporary and permanent failures it returns, naming 4.7.0, 4.7.28, 5.7.1 and 5.7.26, so a rejected sender is told in the SMTP response and the reason is in your bounce logs. What stays invisible is the softer half: mail that is accepted and filed in spam, which nobody reports to you. Validity's 2025 benchmark measured global inbox placement falling to 83.5 percent, with Gmail down almost five percent, and that part shows up only in aggregate.

What is Gmail's spam rate threshold for bulk senders?

Global · Gmail

How email works

In one sentence

Gmail only trusts senders that prove who they are and keep “report spam” rare — under about 0.3%.

Emailrules interpretation

If you send a lot of mail to Gmail (Google’s bulk bar is about 5,000 messages a day to Gmail users), you must prove the mail is really from you and keep spam complaints low. That means public records (, , — see the dotted words), on sending IPs, encrypted delivery (), and on marketing mail. Google wants spam reports near 0.1% and treats 0.3% as the cliff. Under 5,000 a day you still need basic authentication — you do not get a free pass.

Why it matters. If this is wrong, Gmail can reject mail with a clear bounce code or quietly file you in spam. That shows up as “delivered” in your tool and silence from customers.

Dotted words open definitions. See how email actually works.

What to do

Your move — not a lecture

Part platform, part you

The platform covers the mechanical bit. The judgement is still yours.

On a mainstream , branded sending domain setup usually covers , , and one-click . Shared sending IPs are the ESP's problem.

Your part: , list quality, on your domain, and confirming when you run . No platform can stop humans pressing spam for you.

What to do first

Open Google Postmaster Tools and look at over 30 days. If it has touched 0.10 percent, that is your quarter. Then confirm _ and that (if any) have matching .

You can skip this if: You never send to personal Gmail addresses.

Who this applies to

Anyone sending to personal Gmail addresses. The bulk layer applies at about 5,000 messages a day to those addresses. Shared-IP customers still need the to meet and ; branded authentication and remain your problem either way.

Checklist

01Watch in Postmaster Tools and treat 0.10 percent as the ceiling, not 0.30.
02Publish at least p=none once you clear the bulk threshold, and actually read .
03If you use , verify : PTR hostname must resolve back to the same public IP.
04Do not let anyone sell you an ARC mandate for Gmail. The word does not appear on Google's sender guidelines; ARC belongs to Apple and Yahoo.

That’s enough to act. The exact wording, the enforcement record and every primary source sit under Proof & sources, for counsel, bosses, or AI tools that need a citation. Not legal advice.

Proof

Exact position, enforcement, sources

For records and people who will check you. Skip if Monday’s move is already clear.

Source fact

Every sender to personal Gmail accounts needs at least or , valid forward and (PTR) on sending IPs, in transit, RFC 5322 formatting, and a rate under 0.30 percent in Postmaster Tools. Senders of about 5,000 or more messages a day to personal Gmail must use both SPF and DKIM, publish at least p=none, align the , and support for marketing mail. Google asks to stay under 0.10 percent spam and treats 0.30 percent as the line you must never reach. Google's sender guidelines do not mention ARC at all: ARC is Apple's requirement and Yahoo's recommendation, not Gmail's.

What happens if you do not

Less silent than its . Google's own guidelines publish the temporary and permanent failures it returns, naming 4.7.0, 4.7.28, 5.7.1 and 5.7.26, so a rejected sender is told in the SMTP response and the reason is in your bounce logs. What stays invisible is the softer half: mail that is accepted and filed in spam, which nobody reports to you. Validity's 2025 benchmark measured global falling to 83.5 percent, with Gmail down almost five percent, and that part shows up only in aggregate.

Sources

Google, Email sender guidelines
Published 1 Feb 2024Read primary source
Google, Email sender guidelines (Gmail help path)
No publisher dateRead primary source

History of this page

2 Aug 2026Re-verified against primary sources (bulk/auth/consent core).
2 Aug 2026Correction: this page said Gmail enforces silently and that Google scopes ARC to indirect mail. Both were wrong. Google's guidelines name the failures they return (4.7.0, 4.7.28, 5.7.1, 5.7.26), and the word ARC does not appear on the page at all. Re-read both help paths and counted; the ARC claim was traced to a citation that does not exist.
2 Aug 2026Expanded to the all-sender PTR, TLS and RFC 5322 requirements that were missing.
20 Jun 2026Noted the Postmaster v2 reputation dashboard retirement.
2 May 2026Added.

Take this with you

GET https://emailrules.today/rules/gmail-bulk-sender-requirements?format=json

Same URL, same answer, every field including the ones behind the Proof tab. An Accept: application/json header on the plain URL does the same thing. All the endpoints.