It was back in 2023 when Google and Yahoo simultaneously announced that they would start penalizing senders who did not follow their guidelines. The announcement caused some panic because many domains didn’t have DMARC records, some ESPs only DKIM signed messages with a shared domain, and many ESPs did not support RFC 8058 which describes the required one-click unsubscribe mechanism.

Now in 2026 the dust has settled and other providers have since announced enforcement of their own bulk sender requirements to little fanfare; mainly because all of the heavy lifting was done achieving compliance with Google and Yahoo.

Following is a summary of the key sender requirements for the four main consumer mailbox providers as of September 2026.

GoogleYahooMicrosoftApple
Bulk definition5,000+ messages/dayN/A5,000+ messages/dayN/A
ScopeGmail.com and Googlemail.comEverything except yahoo.co.jpOutlook.com and legacy MS domains like hotmail.comiCloud.com
Unsolicited mailNot permittedNot recommendedN/ANot permitted
Unsubscribe LinkRequiredRequiredRequiredRequired
One-Click UnsubscribeRequiredRecommendedN/AN/A
Working From/Reply-ToRequiredN/ARequiredN/A
SPFRequiredRequiredRequiredRequired
DKIMRequiredRequiredRequiredRequired
DMARCRequired and must pass
(p=none is fine)
Required and must pass
(p=none is fine)
Required and must pass
(p=none is fine)
Required and must pass
(p=none is fine)
FCrDNSRequiredRequiredRequiredRequired
Complaint RateIdeally below 0.10%, never exceeding 0.30%Below 0.30%N/AN/A
Link to requirementshere and more information herehere and more information hereherehere

You can see that the requirements are broadly the same across the board and being in compliance with Google more than likely means that you are in compliance with everyone, including providers outside of the ones listed above.

The above is a summary only and I would advise anyone intending to send bulk emails to read the complete requirements for each provider.

More than one of the requirements make reference to Sender Best Common Practices (Version 3.0) produced by the Messaging, Malware and Mobile Anti-Abuse Working Group (M3AAWG) industry group which is definitely worth familiarizing yourself with in addition to provider requirements.