OOmnistu

Blog / Engineering Playbooks

Engineering Playbooks

Sending app emails that reach Gmail: what Google's sender guidelines require

Review Gmail sender requirements for authentication, unsubscribe handling, spam rates and sending practices without assuming guaranteed inbox delivery.

OOmnistu
Reviewed 2026-11-16 · 5 min read
Since February 1, 2024
Every sender to Gmail needs SPF or DKIM, valid forward and reverse DNS, TLS, and a Postmaster Tools spam rate below 0.3%.
Above 5,000 messages a day
SPF and DKIM and DMARC, an aligned From: domain, and one-click unsubscribe for marketing and subscribed mail.
The monitoring bar is tighter
The same page's monitoring advice: keep the spam rate below 0.10% and avoid ever reaching 0.30%.

All wording checked against Google's email sender guidelines linked in Sources; Gmail only, and the guidance does not guarantee delivery.

Most apps send email: sign-up confirmations, password resets, receipts, notifications. When these land in spam or are rejected, users cannot finish signing up, and nothing in the app looks broken. This article summarises what Google's own pages say about sending to personal Gmail accounts, as read on 15 November 2026. Other mail providers have their own rules, which we did not read. Check the pages before you act, because the requirements are updated.

Requirements for every sender

Google's guidelines say that since February 1, 2024 all senders to Gmail accounts must:

Messages that fail authentication might be marked as spam or rejected with a 5.7.26 error, according to the same page. A DKIM key must be 1024 bits or longer to send to personal Gmail accounts, and the page recommends 2048 bits if your domain provider supports it.

Extra requirements above 5,000 messages a day to Gmail

Senders above that volume must use SPF and DKIM and DMARC (the DMARC policy may be set to none), align the From: domain with the SPF or DKIM domain, and support one-click unsubscribe for marketing and subscribed messages with a visible unsubscribe link in the body. The page explains one-click unsubscribe with two headers, List-Unsubscribe and List-Unsubscribe-Post, and points to RFC 2369 and RFC 8058. Do not assume low volume without measuring all relevant sending streams and reviewing Google's bulk-sender classification. Plan authentication and unsubscribe handling early.

What SPF, DKIM and DMARC are, per Google

SPF

A record published for your domain listing who may send for it - include third-party services too.

DKIM

Your server signs outgoing mail with a private key; receivers check it against a public key in your domain's DNS.

DMARC

A published policy telling receivers what to do when checks fail; the policy may be set to none.

Sending practices Google asks for

Monitoring and rate limits, per the same page

Omnistu advice for an app project

Limits

The Gmail guidelines page was read in full on 15 November 2026. The DKIM page was read to the Admin console key step; DNS entry and verification steps were not read and depend on your provider anyway. Gmail only: other providers' rules were not read. No claims about inbox placement rates; Google's guidance does not guarantee delivery either. Local email and privacy law (consent, unsubscribe) were not researched and need counsel.

By Omnistu.

Sources

Previous
DOM-based XSS: when your own JavaScript runs the attack