# Gmail bulk-sender requirements: check authentication and unsubscribe in a delivered email

Inspect a real delivered message, confirm the sender domain and both unsubscribe methods, then verify removal from future sends.

Published: 2026-11-01

Updated: 2026-11-02

Author: Staff Writers

Publisher: Digital Publishing News

Earlier version reviewed by Shaun Connell, Managing Editor

Canonical: https://digitalpublishingnews.com/articles/gmail-bulk-sender-checks/

## Check the message a Gmail recipient actually receives

For a bulk newsletter, a successful send in your email platform does not prove that Gmail’s authentication and unsubscribe requirements are satisfied. Inspect a delivered message, including its technical headers, and test its visible unsubscribe link.

Google’s bulk-sender requirements apply to senders reaching more than 5,000 messages a day to personal Gmail accounts. Authentication checks establish who is allowed to send for a domain and whether that identity matches the address readers see. SPF authorizes sending servers; DKIM adds a verifiable signature; DMARC ties those checks to the visible From domain and specifies a policy.

An email service provider, or ESP, is the platform delivering your newsletter. Its configuration may need work alongside your domain records. Passing authentication alone does not establish all Gmail requirements: transport encryption, domain records, spam rates and unsubscribe behavior also matter.

Source: https://support.google.com/mail/answer/81126?hl=en

## A valid signature can still authenticate the wrong domain

In a delivered Gmail message, open Show original. Compare the visible From domain with the domains reported for SPF and DKIM, then inspect DMARC. Suppose From is editor@publication.example but DKIM authenticates only an unrelated provider domain: that passing signature alone does not establish alignment.

Bulk senders need SPF and DKIM configured. For DMARC alignment, at least one of those authenticated identities must align with the visible From domain; it is not a requirement that both align. A DKIM signature aligned with publication.example can satisfy that part even when SPF uses a different domain.

For marketing and subscribed mail covered by the bulk rules, inspect the one-click headers separately from the visible body link. A working footer does not prove that the header mechanism exists.

Authentication and unsubscribe fields in a delivered message

Delivered-message field | What to inspect

--- | ---

Authentication-Results | SPF, DKIM and DMARC outcomes; which domains authenticated.

From | Whether SPF or DKIM aligns with the visible domain.

List-Unsubscribe | The secure web address used for one-click unsubscribe.

List-Unsubscribe-Post | List-Unsubscribe=One-Click

Message body | A clearly visible unsubscribe link.

## Finish with an actual suppression test

Use a controlled subscriber to unsubscribe, then confirm that address is excluded from the next marketing send. A successful link response without suppression leaves the reader receiving unwanted mail.

Keep spam rates in Google’s Postmaster Tools, its sender-reporting service, below 0.3%; that ceiling is not a target. Ask the sending operator to verify TLS, encryption between mail servers, and DNS, the domain records identifying the sending servers.

Give the email provider the actual failing result and authenticated domains, not a general request to confirm compliance. Repeat this delivered-message check after a provider or sending-domain change. These checks cover authentication and unsubscribe behavior; the other sending requirements still apply.

## Test more than one real mailing path

Repeat the delivered-message check for each stream that uses different sending infrastructure. A newsletter campaign and a billing receipt may come from different tools even if readers see the same brand. Record the sending path, the domain visible to recipients, and the result of the unsubscribe check where applicable. Use an address you control so the test does not subscribe or unsubscribe a customer.

## Find the sender that is actually failing

Imagine campaign mail passes alignment, but a message sent after signup does not. Compare the received headers on each message and note the tool that generated it. The two paths may use the same visible brand and different infrastructure. A successful newsletter test therefore gives you evidence for only that path.

Keep a small inventory of real delivered messages: newsletter, signup confirmation and any separate program that uses a different sender. For each relevant stream, check alignment and whether the unsubscribe action persists through the next eligible send. Record the account and message you used for the test. This lets a teammate reproduce the result rather than relying on a screenshot of a settings page.

AI production disclosure: https://digitalpublishingnews.com/how-we-use-ai/

## Sources

https://support.google.com/mail/answer/81126?hl=en

Editorial status: AI-assisted revision; preceding edition reviewed by Shaun Connell. Current revision awaits review.