Meeting Bulk Sender Requirements for Gmail

The requirements at a glance

SPF and DKIM on every message. Not one of the two — both. And the signing domain has to match the sender address.
A DMARC record, at least p=none. The bar is set low, but it is a bar: no record, no bulk delivery.
Alignment of the sender address. The domain in the visible From must match the one that passed SPF or DKIM. A provider signing with their own domain does not satisfy this.
One-click unsubscribe in promotional and newsletter mail, honoured within two days. Details in Set up List-Unsubscribe.
Complaint rate below 0.3 %, sustained. The target is 0.1 % — 0.3 % is where filtering begins, not the goal.
Valid forward and reverse resolution of the sending IP, and delivery over TLS.
Formally correct messages per RFC 5322 — in particular a valid Message-ID and Date header and a From carrying exactly one address.

Where it actually breaks down

The technical points are an afternoon's work. What actually costs deliverability is almost always the complaint rate — and that cannot be configured.

0.3 % means three recipients in a thousand press “spam”. It sounds like a lot and is comfortably exceeded with purchased addresses, old lists and a hard-to-find unsubscribe. The most effective lever is, paradoxically, an easy unsubscribe: someone who can leave does not press spam. Each spam marking weighs many times an unsubscribe in the assessment.

What counts as bulk

The threshold refers to messages to one provider per day, counted across the sender domain — not to total volume. Once exceeded, the status persists, quiet days included.

Sitting just below is no exemption: the same criteria feed into the assessment regardless, only without the hard threshold. So suppressing volume to stay under the line is not worth it.

Separate transactional from promotional mail

Invoices, password mails and order confirmations should not travel over the same domain as the newsletter. Two reasons:

The unsubscribe requirement applies to promotional mail, not transactional. An unsubscribe link under an invoice is pointless and in places legally awkward.
Complaints about the newsletter would otherwise damage delivery of the password mails — and that failure only surfaces when customers can no longer sign in.

The clean separation runs through subdomains, for instance news.yourdomain.com for promotion and the main domain for everything else. It relieves the SPF lookup budget along the way.

Check before it counts

Whether a message satisfies the technical points shows not in the DNS entry alone but in the message as sent. A mail to hello@analyzemy.email checks SPF, DKIM, DMARC alignment, TLS, reverse resolution and the headers on a real delivery.

What AnalyzeMy.Email checks for this

Bulk Sender Checklist — Turns the requirements Gmail, Yahoo and Microsoft place on bulk senders into a checklist and checks every point that can be read from a single delivered message.

List-Unsubscribe & One-Click — When one-click unsubscribe per RFC 8058 applies — the report checks a real message's unsubscribe addresses, the Post header and whether a valid DKIM signature covers both headers.

MIME Structure — How an email is put together — the report breaks down its MIME structure: content type, which parts exist, the order of text and HTML, and the text-to-image ratio.

DMARC Check — Validates the DMARC record, evaluates SPF and DKIM alignment, and audits the policy for weaknesses — from p=none through pct to the subdomain policy.

SPF Check — Validates your domain's SPF TXT record and whether the sending server is authorized — including a full audit of the record against RFC 7208.

DKIM Check — How DKIM signs outgoing mail — the report verifies every signature in the message against the key in DNS and checks alignment with the From header.

Header Analysis — What an email's headers reveal — the report checks them SpamAssassin-style: Message-ID, date, MIME-Version, Reply-To mismatch, duplicate From headers, X-Mailer and subject.

Bulk Sender Requirements — What Google and Yahoo Demand