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.
- 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:
- set up SPF or DKIM authentication for their sending domains;
- have valid forward and reverse DNS records for sending IPs or domains;
- use a TLS connection to send email;
- keep the spam rate reported in Postmaster Tools below 0.3%;
- format messages to the Internet Message Format standard (RFC 5322);
- not impersonate Gmail From: headers.
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. The page says to include all your senders, including third-party services, or their mail is more likely to be marked as spam.
- DKIM: your mail server signs outgoing messages with a private key and receivers check the signature against a public key published in your domain's DNS. Google's DKIM page describes it as protection against spoofing.
- DMARC: a published policy for messages that fail DMARC. A message can pass through either aligned SPF or aligned DKIM; it does not need both to pass DMARC. Domain alignment follows the configured relaxed or strict mode, not necessarily exact hostname equality. The page recommends turning on DMARC reports to see who is sending as your domain. If you use an email service provider, Google says to verify that the provider authenticates your domain with SPF and DKIM.
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
- Send only to people who opted in, confirm each address before subscribing, and make unsubscribing easy. The page warns against buying lists and pre-checked opt-in boxes, and notes some countries restrict automatic opt-in (we have not researched laws).
- Use the same From: address for the same category of message, for example receipts, promotions and account notifications each from their own address; do not mix promotions into receipts; ideally send from one IP address, or use a different IP for each message type.
- Do not hide content with HTML or CSS, avoid misleading subject lines such as a fake "Re:", keep links visible and understandable, and use display names only to identify the sender (not subject text, the recipient's name or emojis).
- On shared IP addresses, other senders' behaviour affects your reputation, so check blocklists and use Postmaster Tools.
- Increase sending volume gradually: Google says to start with engaged users, send at a steady rate, avoid sudden spikes, and monitor spam rate and reputation as volume grows.
Monitoring and rate limits, per the same page
- The requirements say to keep the Postmaster Tools spam rate below 0.3%. The monitoring section goes further: keep it below 0.10% and avoid ever reaching 0.30% or higher.
- Google says it does not track open rates and cannot verify open rates reported by third parties, so a low open rate is not necessarily a sign of a delivery problem.
- If you exceed a quota, Gmail typically rejects with SMTP error 4.7.28. The page says to stop sending for at least 10 minutes, find the cause, then resume from a single connection. This applies to bulk senders more than a small app.
- Google says it does not accept allowlist requests from email providers and cannot guarantee that provider mail passes its spam filters.
Omnistu advice for an app project
- Treat email as part of the launch checklist: decide which domain sends, which provider, and who controls the DNS.
- Use separate addresses for transactional messages (resets, receipts) and marketing, as Google suggests by message category, to separate message categories operationally. Different addresses alone do not isolate domain or IP reputation, so do not promise protection for password resets.
- Have the developer show you the SPF, DKIM and DMARC records and a test message with the authentication results, as one concrete proof.
- Register the domain in Google Postmaster Tools, and agree who watches the spam rate.
- Do not ship an email feature that sends before authentication is set up; test with a few of your own addresses first.
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.