Transactional email explained: what it is and what Gmail requires from senders
Password resets, receipts and alerts are transactional email - how they differ from marketing mail, and what Google's sender guidelines require for delivery.
Transactional email is the mail your app owes its users: password resets, receipts, booking confirmations and security alerts. It is different from marketing mail, and it has to arrive. Google's email sender guidelines - which apply to mail sent to personal Gmail accounts - spell out what that takes, and they have applied to all senders since February 1, 2024. Here is the shape of the rules.
What every sender must do
For any volume, Gmail expects you to set up SPF or DKIM authentication for your sending domains, keep valid forward and reverse DNS records (PTR records) for sending domains or IPs, transmit over TLS, keep the spam rate reported in Postmaster Tools below 0.3%, format messages according to the internet message format standard (RFC 5322), and avoid impersonating Gmail From: headers - Gmail uses a DMARC quarantine enforcement policy, and impersonation can hurt delivery.
The 5,000-a-day line
Send more than 5,000 messages a day to Gmail accounts and the requirements grow: both SPF and DKIM plus DMARC (the enforcement policy may be set to none), a From: header domain aligned with the SPF or DKIM domain, and - for marketing and subscribed messages - one-click unsubscribe plus a clearly visible unsubscribe link in the body.
Why authentication decides delivery
Authenticated messages protect recipients from spoofing and phishing, protect you from being impersonated, and are less likely to be rejected or marked as spam; Gmail notes that unauthenticated messages may be marked as spam or rejected with a 5.7.26 error. If you send through an email service provider, verify that it authenticates your domain with SPF and DKIM.
The calm version
Authenticate every sending domain, keep complaints low, and treat unsubscribing as a feature rather than a loss. The full checklist lives in Google's guidelines - and the mechanics of SPF, DKIM and DMARC themselves are covered in our email authentication guide.
Source: Google Email sender guidelines (support.google.com/mail/answer/81126, fetched 2026-11-20) - requirements for all senders, bulk-sender requirements above 5,000 messages/day, spam-rate threshold, and authentication rationale. Delivery outcomes depend on many factors; meeting the guidelines is a requirement, not a delivery guarantee.
Frequently asked questions
What counts as transactional email?
Mail a user triggers or relies on - password resets, receipts, alerts. Google's guidelines distinguish it from marketing and subscribed messages, which carry extra unsubscribe duties for bulk senders.
Does a small sender need DMARC?
All senders need SPF or DKIM. Senders of more than 5,000 messages a day to Gmail accounts must also set up DMARC - the policy may be none - with an aligned From: domain, and one-click unsubscribe for marketing mail.
What happens if my mail is not authenticated?
According to Google, unauthenticated messages might be marked as spam or rejected with a 5.7.26 error.
What spam rate is acceptable?
Keep the spam rate reported in Postmaster Tools below 0.3%.