What Gmail and Yahoo now require from senders

Authentication is no longer optional. What changed, who it applies to, and what a shop owner actually has to do about it.

✉️ MailMedic6 min readUpdated 2026-08-22

In 2024 Gmail and Yahoo stopped treating email authentication as a recommendation. Both now enforce a baseline for everyone, and a stricter set of rules for anyone sending in volume. Microsoft has been moving the same direction. If your shop sends order confirmations, shipping notices and the occasional campaign, this affects you.

The baseline for every sender

Any domain sending mail is expected to have at least one form of authentication — SPF or DKIM — plus valid forward and reverse DNS on the sending server. Mail from a domain with neither is increasingly filtered outright rather than merely scored down.

The stricter set for bulk senders

Sending roughly five thousand messages a day or more to a single provider puts you in the bulk category. Then all of the following are expected:

The exact thresholds are set by Gmail and Yahoo and can change. Treat the numbers above as the direction of travel rather than a contract, and check the providers' own postmaster documentation when a specific figure matters to you.

Why a small shop should still care

Two reasons. First, the daily volume threshold is per provider and easier to cross than it sounds during a busy campaign week. Second, and more importantly, the baseline already applies to you today. A shop with no SPF and no DKIM is exactly the profile these rules were written to filter.

There is also a Shopify-specific trap. Shopify sends your transactional mail on your behalf, from its own infrastructure. If your SPF record does not include Shopify, every order confirmation fails authentication — while the mail you send by hand from the same domain arrives perfectly. Shop owners chase this for weeks because their own tests always look fine.

What to actually do

  1. Check where you stand. Run your domain through a checker and see which of the four records fail.
  2. Fix SPF first, and make sure it includes every service that sends for you — the store platform, your mailbox provider, your marketing tool.
  3. Turn on DKIM in each sending service and publish the key it gives you.
  4. Publish a DMARC record at p=none with reporting enabled, and leave it for a couple of weeks.
  5. Read the reports, fix whatever legitimate sender is failing, then move to p=quarantine and eventually p=reject.

The whole path usually takes a shop four to six weeks, most of which is waiting for reports rather than working. There is no benefit to rushing it, and a real cost to going straight to enforcement and blocking your own invoices.

Complaint rate is the requirement people forget, and it is not a DNS setting. It comes down to only mailing people who asked, making unsubscribing trivial, and not sending more often than you promised. Every reminder our own Repeatly app sends has a one-click unsubscribe for exactly this reason.
Did this answer your question?

If anything here was wrong, unclear or out of date, tell us — the article gets fixed the same day.

Related articles