Gmail evaluates sender identity, technical authentication and recipient response together. A passing DNS record is only one part of the requirement. Use this checklist before increasing volume to personal Gmail accounts.
1. Know when bulk-sender rules apply
Google treats a sender delivering about 5,000 or more messages to personal Gmail accounts in one day as a bulk sender. The status is based on the primary domain and is not a temporary label that can be reset by changing a subdomain. Separate transactional and promotional traffic operationally, but review compliance across the full sending domain.
2. Build the authentication baseline
All senders need SPF or DKIM, valid forward and reverse DNS, TLS, RFC 5322 formatting and low user-reported spam. Bulk senders need SPF and DKIM, DMARC, From-domain alignment through SPF or DKIM, and one-click unsubscribe for promotional or subscribed messages.
3. Protect the recipient experience
Use a recognizable From name, honest subject, visible unsubscribe link and relevant audience. Keep Gmail Postmaster spam rate below 0.1% as an operational target and prevent it from reaching 0.3% or higher. Stop a campaign when complaint growth or authentication failures appear.
4. Preflight before scale
Test SPF, DKIM, DMARC alignment, TLS, PTR and message formatting with the same route and From domain that production will use. Verify that the unsubscribe endpoint works without requiring a login, and confirm that suppression is applied before the next campaign.
Implementation checklist
- SPF and DKIM pass
- DMARC record exists
- From domain aligns with SPF or DKIM
- Forward and reverse DNS match
- TLS is used
- RFC 5322 formatting passes
- One-click unsubscribe works for promotional mail
- Postmaster spam rate stays below the stop threshold
Primary references
Share the sending domain, route, message purpose, expected volume and a recent received-message header.
Request technical review