Google and Yahoo sender requirements

What changed in 2024

Google and Yahoo tightened bulk-sender rules. They did not invent authentication, and they did not make warmup optional. They made the ID check mandatory and they started enforcing complaint rates that cold email was already supposed to stay under.

In practice, for anyone sending cold email toward Gmail or Yahoo:

• SPF and DKIM must pass alignment
• DMARC must be present (EmailPal uses p=reject)
• Spam complaint rates must stay tiny (Google has talked about staying under 0.3%, and treating 0.1% as the healthy zone)
• Marketing / bulk mail needs a working unsubscribe, including one-click where the standard applies

EmailPal's job is the authentication and the sending reputation of the mailbox. Your sequencer still has to honor unsubscribes. We do not run the campaign UI.

Yahoo and AOL sit in the same family of expectations. That is one reason EmailPal warming seeds include Gmail, Yahoo and AOL, not only Gmail.

What EmailPal already does

On hosted domains we publish:

• MX so replies can land
• SPF v=spf1 include:_spf.emailpal.io -all
• DKIM at rsa._domainkey (RSA-2048) and ed._domainkey (Ed25519)
• DMARC p=reject

Then we re-verify those records on public resolvers. A green check means Gmail's lookup of your domain will see the same values. How to set up DNS records (MX, SPF, DKIM, DMARC).

Warming talks to real Gmail, Yahoo and AOL accounts, which is the same universe those requirements came from. Pre-warmed listings attach the inbox rate measured on that network. Email warming by EmailPal.

Isolated IP pools keep one customer's list from defining another customer's reputation. Isolated IP pools.

What you still have to do

• Verify lists so you are not mailing dead addresses. Bounces and catch-alls are how complaint rates and block rates start. List verification.
• Keep per-mailbox volume modest. Sending limits: 40/day on plan mailboxes, 15/day on pre-warmed.
• Put an unsubscribe path in the campaign tool you actually send from. EmailPal is infrastructure, not the sequence UI. One-click unsubscribe is a header the sequencer must set.
• Stay off the company .com. Secondary sending domains.
• Do not turn open tracking on for the first mail from a new or newly claimed mailbox. Bot opens are not engagement.

The full checklist: Cold email deliverability guide.

What "bulk sender" means for cold email

Google's threshold has been in the neighborhood of 5,000 messages per day to Gmail. Cold programs often sit under that per domain and still get treated like bulk because the copy, the list and the sudden volume look like bulk.

Do not plan around "we send 4,900 so the rules do not apply." Authenticate anyway. EmailPal will not let you send unauthenticated mail from a hosted domain.

FAQs

Does p=reject satisfy Gmail?

Yes. They asked for a DMARC policy to exist. Reject is stronger than none, and it is what EmailPal ships. Why DMARC is p=reject.

Do I need BIMI?

No. BIMI is a brand logo for high-volume authenticated senders. It is not required for cold email and will not save a burned domain.

Does EmailPal add List-Unsubscribe headers?

Not on mail you send through Instantly or Smartlead. Those tools own the campaign headers. Mail you send through EmailPal's own send API follows what that API documents.

Will a pre-warmed inbox automatically pass Gmail?

It is authenticated and it finished a measured ramp. That is the infrastructure half. A scraped list and a three-link HTML pitch can still land in spam. The 15/day cap is how we keep the measurement from collapsing; it is not a Gmail SLA.

What about Microsoft?

Microsoft is often harsher on new domains than Gmail. The 2024 headlines were Google and Yahoo. Outlook still wants authentication and still punishes volume spikes. Slow down rather than chasing the worse provider with more volume.

Need more help?

Cold email deliverability guide or open a ticket with the domain and whether you send via SMTP to a sequencer or via our API.