Do I need…to comply with the bulk sender requirements?

YES

(law at 5,000 a day)

Since 2024, Gmail, Yahoo, Microsoft, and Apple enforce the same baseline on bulk senders: full authentication, one-click unsubscribe, complaints under 0.3%. Below the threshold you're graded on it anyway.

Learn more Ask another
The long answer ↓

Between 2024 and 2025 the major mailbox providers stopped treating sender best practices as suggestions. Gmail and Yahoo enforced first (February 2024), Apple hardened its recommendations into requirements, and Microsoft joined in May 2025—with SMTP-level rejections (550 5.7.515) for senders who fail authentication.

Who’s a “bulk sender”

The consistent threshold is 5,000 or more messages a day to a provider’s consumer domains (gmail.com, yahoo.com, outlook.com/hotmail.com/live.com). It targets newsletters, promotions, and campaigns rather than triggered transactional mail—but the practices apply to everyone, and enforcement mechanisms don’t always check your volume badge first.

The requirements, in one place

  1. Authenticate fully. SPF, DKIM, and a DMARC policy—p=none satisfies the requirement; the point is that a policy exists and your mail aligns with it.
  2. One-click unsubscribe. The RFC 8058 List-Unsubscribe + List-Unsubscribe-Post headers on bulk mail, honored within two days—details here—plus a visible unsubscribe link in the body.
  3. Complaints under 0.3%. The hard ceiling; healthy senders sit under 0.08%. This is the requirement that punishes bought lists and lazy targeting, and the one you monitor continuously.
  4. Valid sender addresses. Microsoft additionally requires that your From and Reply-To addresses actually accept mail—one more reason no-reply@ is a bad habit.

Why comply below the threshold

Because the requirements are just deliverability fundamentals with enforcement attached. Authentication, easy exits, and low complaints are how mail lands in inboxes at any volume—and if you’re growing, crossing 5,000/day with these already in place is a non-event instead of a scramble. A good ESP handles the mechanical parts by default (Resend requires domain authentication and sets the unsubscribe headers on Broadcasts automatically); the list quality half is yours.

The one-page version: authenticate, make leaving easy, send to people who want it. The providers didn’t invent new rules—they started enforcing the old ones.