Gmail and Yahoo require bulk senders (5,000+ messages/day) to: authenticate with SPF, DKIM, and DMARC; support one-click unsubscribe via List-Unsubscribe headers; maintain spam complaint rates below 0.3% (Gmail recommends under 0.1%); use a valid forward DNS (FCrDNS) on sending IPs; and format messages per RFC 5322. This checklist covers every requirement with verification steps.
Gmail and Yahoo Bulk Sender Checklist: Every Requirement on One Page
The Bulk Sender Quick-Reference Checklist
Use this as a verification checklist. For detailed implementation, see our complete bulk sender requirements guide.
Authentication Requirements
SPF
- SPF record published for your sending domain
- All sending IPs included in SPF record
- SPF passes for outgoing mail (verify with email headers)
Verify: Send a test email to Gmail, view headers, check spf=pass.
DKIM
- DKIM signing enabled for your sending domain
- DKIM key is 1024-bit or larger (2048-bit recommended)
- DKIM signature passes verification
Verify: Send a test email to Gmail, view headers, check dkim=pass.
DMARC
- DMARC record published:
_dmarc.yourdomain.com - Policy is at least
p=none(p=quarantine or p=reject preferred) - Either SPF or DKIM alignment passes (preferably both)
Verify: dig _dmarc.yourdomain.com TXT returns a valid DMARC record.
Practitioner note: DMARC at p=none is the minimum. Gmail accepts it, but you're leaving yourself exposed to spoofing. Plan your path to p=reject — it's better for deliverability and security.
Infrastructure Requirements
PTR Records (Reverse DNS)
- Every sending IP has a valid PTR record
- PTR record resolves back to the sending IP (Forward-confirmed reverse DNS)
Verify: dig -x YOUR_IP_ADDRESS returns a hostname, then dig THAT_HOSTNAME returns your IP.
TLS
- Sending servers support TLS 1.2+
- Opportunistic TLS enabled for all outgoing connections
Most ESPs handle this automatically. If you run your own infrastructure, verify your MTA configuration.
RFC 5322 Compliance
- Valid Message-ID header
- Valid Date header
- Properly formatted From header
- No duplicate headers
Verify: Send to Gmail, check headers for compliance warnings.
One-Click Unsubscribe
-
List-Unsubscribeheader present in all marketing email -
List-Unsubscribe-Post: List-Unsubscribe=One-Clickheader present - Unsubscribe URL is HTTPS
- Unsubscribe processes without requiring user input (truly one-click)
Verify: Send to Gmail, check email headers for both List-Unsubscribe and List-Unsubscribe-Post.
Practitioner note: The one-click unsubscribe requirement means the unsubscribe URL must process a POST request without any user interaction. If your unsubscribe link goes to a confirmation page, that's not one-click. Most ESPs handle this correctly, but custom implementations often get it wrong.
Spam Rate Requirements
- Spam complaint rate stays below 0.3% (Gmail's hard limit)
- Target complaint rate under 0.1% (Gmail's recommendation)
- Monitoring complaint rate via Google Postmaster Tools
Verify: Check Google Postmaster Tools → Spam Rate dashboard.
If Your Spam Rate Is Too High
- Stop sending to unengaged subscribers immediately
- Review recent campaigns for content issues
- Check for list quality problems (purchased lists, old data)
- Verify unsubscribe mechanism is visible and functional
- Monitor daily until rate drops below 0.1%
Message Format Requirements
- From domain matches the domain in your DKIM signature or SPF record (alignment)
- No impersonation of Gmail "from:" headers
- ARC headers added if you modify or forward messages
- Marketing email clearly distinguishable from personal email
Monitoring and Verification
Google Postmaster Tools Setup
- Go to postmaster.google.com
- Add your sending domain
- Verify ownership via DNS TXT record
- Monitor: Spam Rate, IP Reputation, Domain Reputation, Authentication
Regular Checks
| Check | Frequency | Tool |
|---|---|---|
| Spam complaint rate | Daily during campaigns | Google Postmaster Tools |
| Authentication pass rates | Weekly | Google Postmaster Tools |
| Domain reputation | Weekly | Google Postmaster Tools |
| Unsubscribe functionality | Before every campaign | Manual test |
| PTR records | Monthly | dig / nslookup |
If you need help getting compliant with bulk sender requirements, book a deliverability audit.
Sources
- Google: Email Sender Guidelines
- Yahoo: Sender Requirements
- RFC 8058: One-Click Functionality for List-Unsubscribe
- Google: Postmaster Tools
v1.0 · April 2026
Frequently Asked Questions
What are the Gmail bulk sender requirements?
SPF and DKIM authentication, DMARC at p=none minimum, one-click unsubscribe via List-Unsubscribe header, spam complaint rate under 0.3%, valid PTR records on sending IPs, RFC 5322 compliant messages, TLS for transmission, and no Gmail impersonation.
How do I check if I'm a bulk sender?
If you send 5,000 or more messages to Gmail addresses in a single day, you're a bulk sender. This is counted per sending domain, not per IP. Check Google Postmaster Tools for your daily send volume to Gmail.
What happens if I don't comply with bulk sender requirements?
Gmail will temporarily reject messages with 4xx errors, allowing you to fix compliance issues. Continued non-compliance leads to permanent rejection or spam folder placement. Yahoo implements similar enforcement.
Want this handled for you?
Free 30-minute strategy call. Walk away with a plan either way.