| Bulk threshold | 5,000+ messages/day to personal Gmail from same primary domain triggers bulk-sender status. | Treat high volume as needing authentication, reputation, and unsubscribe hygiene. | 5,000+ messages/day to Outlook.com domains triggers SPF/DKIM/DMARC enforcement. | If near 5,000/day to any major mailbox provider, run full bulk-sender readiness before scale. |
| Enforcement mode | As of Nov 2025, Google rejects non-compliant bulk mail at the SMTP server level (not just spam-foldering). Postmaster Tools v2 reports binary Pass/Fail compliance. | Expect rejection-style enforcement to follow the Google/Microsoft direction; verify current Yahoo policy before scale. | As of 2025, Microsoft rejects unauthenticated senders at 5,000+/day with error 550 5.7.515 (Junk-foldering began 2025-05-05, then rejection). | Treat authentication/compliance failure as a hard send block — mail is rejected at the server, not merely junked. In 2026, low opens are more likely a compliance/placement failure than a copy failure. |
| SPF | Required for bulk senders. | Required/best practice. | Required for high-volume senders. | Block scale until SPF passes for every sending domain/provider. |
| DKIM | Required for bulk senders. | Required/best practice. | Required for high-volume senders. | Block scale until DKIM signs correctly. |
| DMARC | Required for bulk senders with at least p=none; From alignment matters. | Required/best practice. | Required for senders at 5,000+/day; failures rejected with 550 5.7.515 (as of 2025). | Block scale until DMARC exists and aligns with sender identity. |
| Forward/reverse DNS | Google requires valid PTR and matching forward DNS for sending IPs. | Sender infrastructure should identify sending sources clearly. | Sender reputation depends on clean authenticated infrastructure. | For shared ESPs, verify provider handles this. For owned infrastructure, block until DNS is correct. |
| TLS | Google requires TLS for bulk senders. | Use modern authenticated mail infrastructure. | Use compliant authenticated mail infrastructure. | Block if sender cannot confirm TLS support through ESP/MTA. |
| Header accuracy | Google flags malformed or deceptive headers/content. | Sender identity and message authenticity matter. | Authentication and non-deceptive identity matter. | Reject deceptive From, Re:, Fwd:, hidden content, spoofed identity, or unclear sender. |
| One-click unsubscribe | Required for marketing/promotional bulk mail and must be honored quickly. | Required/recommended for bulk and commercial senders. | High-volume senders should support compliant unsubscribe practices. | For scaled cold campaigns, include unsubscribe handling and suppression workflow. |
| Complaint rate | Google says keep user-reported rate below 0.1% and avoid 0.3% or higher. | Complaints affect reputation and delivery. | Reputation/complaints affect junking and blocking. | Stop or narrow if complaints rise. Do not increase volume to compensate. |
