Home / Guides / Requirements

Gmail and Yahoo sender requirements explained

What Gmail and Yahoo demand from every sender and from bulk senders since February 2024, and exactly how to meet each requirement.

7 min read · Updated 27 October 2026 · By the dijitul team

Since February 2024, Gmail and Yahoo have required every sender to authenticate their email and keep spam complaints low, with stricter rules for anyone sending in bulk. If you send close to 5,000 or more messages a day to Gmail addresses, you need SPF, DKIM and DMARC, aligned with your From domain, plus one-click unsubscribe and a spam rate below 0.3%. Below that volume you still need SPF or DKIM, valid DNS and a clean complaint record.

Here is what each rule means in practice and how to meet it, without the jargon.

Two tiers: all senders and bulk senders

The requirements come in two layers. Everyone sending to Gmail or Yahoo has to meet the first layer. Bulk senders have to meet both.

RequirementAll sendersBulk senders
SPF or DKIM authenticationRequired (at least one)Both required
DMARC record (p=none or stricter)RecommendedRequired
From domain aligned with SPF or DKIMRecommendedRequired
Valid forward and reverse DNS for sending IPsRequiredRequired
TLS for transmitting emailRequiredRequired
RFC 5322 message formattingRequiredRequired
Spam rate below 0.3%RequiredRequired
One-click unsubscribe (RFC 8058), honoured within 2 daysNot requiredRequired for marketing and subscribed mail

What counts as a bulk sender

Google defines a bulk sender as one that sends close to 5,000 or more messages to personal Gmail accounts within 24 hours. Three details catch people out:

  • It is counted per domain. Mail from all your systems that use the same primary domain counts together: newsletters, receipts, CRM sequences and staff email.
  • It only takes one day. A single large campaign that crosses the threshold is enough.
  • It is permanent. Once you have been treated as a bulk sender, Google keeps treating you as one, even if your volume drops afterwards.

Yahoo applies very similar rules but has not published a fixed number. The safest approach is to meet the bulk requirements regardless of size. None of them are expensive, and they help your deliverability everywhere, including Microsoft, which introduced its own bulk-sender rules in May 2025.

Each requirement and how to meet it

SPF and DKIM

SPF is a DNS TXT record listing the services allowed to send for your domain. DKIM is a signature added to each message, checked against a public key published in your DNS. Every service that sends as your domain needs to be covered: your mailbox provider, newsletter tool, CRM, helpdesk, invoicing system and website. Our guides to SPF records and DKIM cover setup in detail, and if you use Google Workspace or Microsoft 365, see Google Workspace authentication or Microsoft 365 authentication.

DMARC and alignment

Bulk senders must publish a DMARC record with a policy of at least p=none. A minimal starting record looks like this, published as a TXT record at _dmarc.yourdomain.co.uk:

v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.co.uk

Alignment means the domain that passes SPF or DKIM matches the domain in your visible From address. A common failure: your newsletter platform signs DKIM with its own domain and uses its own bounce domain for SPF. Both checks "pass", but neither aligns, so DMARC fails. The fix is to set up the platform's custom domain authentication, which usually means adding a few CNAME records it gives you. See the DMARC guide for how to read reports and tighten the policy later.

Forward and reverse DNS

The IP address your mail leaves from needs a PTR (reverse DNS) record pointing to a hostname, and that hostname must resolve back to the same IP. If you send through a major provider this is handled for you. If you run your own mail server, ask your host to set it. See reverse DNS and PTR records.

TLS

The connection used to deliver your mail must be encrypted with TLS. Any modern email service does this by default. It mainly matters for self-hosted servers and old devices such as scanners or alarm systems that send email directly. For extra protection on incoming mail, see MTA-STS and TLS-RPT.

Message formatting

Messages must follow RFC 5322, the standard for email format. In practice: exactly one From header, a valid Date and Message-ID, and no malformed headers. Do not put a Gmail address in your From header when sending through another service, because that impersonates Gmail and will fail DMARC.

One-click unsubscribe

Marketing and subscribed messages from bulk senders must include two headers that let Gmail and Yahoo show an unsubscribe button and process it in a single click:

List-Unsubscribe: <https://yourdomain.co.uk/unsubscribe?id=abc123>, <mailto:unsubscribe@yourdomain.co.uk?subject=unsubscribe>
List-Unsubscribe-Post: List-Unsubscribe=One-Click

The HTTPS address must accept a POST request and unsubscribe the person without asking them to log in or confirm. Both headers must be covered by your DKIM signature. You still need a visible unsubscribe link in the body, and requests must be honoured within two days. Transactional messages such as password resets and order confirmations are exempt. Most email platforms add these headers automatically; our one-click unsubscribe guide explains how to check.

Check your setup now: run a free test at mail-tester.co.uk and see your score in seconds.

Spam rate below 0.3%

This is the user-reported spam rate: the share of your delivered messages that Gmail users mark as spam. Keep it below 0.3% and aim for under 0.1%. The best levers are simple: only email people who opted in, make it obvious who you are, make unsubscribing easy (people who cannot find the link click "report spam" instead), and stop sending to people who never engage.

Google Postmaster Tools

Google Postmaster Tools is a free dashboard that shows how Gmail sees your domain. To use it, sign in with a Google account, add your domain and verify it with a TXT record in your DNS. Once you send enough volume, it shows your spam rate, authentication results, encryption and delivery errors, along with a compliance status view showing whether you meet the sender requirements.

Data only appears once you send a meaningful amount of mail to Gmail users, so smaller senders may see little or nothing. That is normal. Yahoo offers a sender hub and a complaint feedback loop for senders who want to receive spam complaint reports.

Domains, DNS & emaildijitul DNSRegister and transfer .uk and .com domains, with Cloudflare DNS management and business email. SPF, DKIM and DMARC set up properly.Fix your DNS with dijitul

What happens if you fail

Non-compliant mail is not always blocked outright. Google phased enforcement in gradually: first temporary errors for a share of non-compliant traffic, then rejections. In practice you are likely to see a mix of:

  • Messages landing in spam rather than the inbox.
  • Temporary deferrals, where Gmail returns a 4xx error and your server retries later.
  • Outright rejections with a 5xx error. The bounce message usually links to Google's sender guidelines and names the failed requirement, so always read it.
  • Loss of eligibility for mitigation if your spam rate stays high, meaning Google will not help you fix delivery problems until you get it back under control.
If your bounces mention authentication or "unauthenticated email", fix SPF, DKIM and DMARC before anything else. No amount of content tweaking will get unauthenticated mail into Gmail.

A quick compliance plan

  1. List every service that sends email as your domain.
  2. Make sure each one is in your SPF record and signs DKIM with your domain.
  3. Publish a DMARC record at p=none with a reporting address.
  4. Send a test from each service and confirm SPF, DKIM and DMARC pass with alignment.
  5. Check that marketing emails carry both List-Unsubscribe headers.
  6. Set up Google Postmaster Tools and watch the spam rate after each campaign.

Our test includes a Gmail, Yahoo and Microsoft compliance checklist, so you can see in one report which requirements you already meet and which still need work.

Frequently asked questions

What counts as a bulk sender for Gmail?

Google treats you as a bulk sender if you send close to 5,000 or more messages to personal Gmail accounts in a 24-hour period. All messages from your primary domain count towards the total, and once you reach that level Google treats you as a bulk sender permanently.

Do the Gmail requirements apply to small businesses?

Yes. The bulk-sender rules only apply above the volume threshold, but the all-sender rules apply to everyone: SPF or DKIM, valid forward and reverse DNS, TLS, properly formatted messages and a low spam complaint rate.

Is DMARC p=none enough for Gmail and Yahoo?

For the bulk-sender rules, yes. A DMARC record with at least p=none is required, and SPF or DKIM must align with your From domain. Moving to quarantine or reject later gives you stronger protection against spoofing.

How quickly must unsubscribes be processed?

Bulk senders must support one-click unsubscribe as defined in RFC 8058 and honour unsubscribe requests within two days.

What spam rate do Gmail and Yahoo allow?

Keep the user-reported spam rate shown in Google Postmaster Tools below 0.3%. Google recommends staying under 0.1%.

From the team behind Mail Tester UK

More from dijitul