- Set up SPF, DKIM and DMARC, align them with your From domain, then move DMARC to enforcement.
- Add one-click unsubscribe headers and honor every unsubscribe within two days.
- Keep your spam complaint rate under 0.1% in Google Postmaster Tools. Never let it reach 0.3%.
- Remove bounces and complainers automatically, and sunset readers who stopped engaging.
- Warm up any new domain or platform before you send to the full list.
- Keep cold outreach off your newsletter domain.
- Read open and click data with care. Privacy features and security scanners inflate both.
The rules you are sending under
Since February 2024, Gmail and Yahoo have required authentication and easy unsubscribes from bulk senders. Microsoft followed for Outlook.com, Hotmail and Live addresses in May 2025. These are no longer best practices. They are the entry ticket.
| Provider | Who it applies to | What they require |
|---|---|---|
| Gmail | Senders of about 5,000 or more messages a day to personal Gmail accounts, counted across your whole domain | SPF and DKIM, DMARC aligned with your From domain (p=none is accepted), one-click unsubscribe, spam rate under 0.3% |
| Yahoo | Bulk senders | SPF and DKIM, a valid DMARC policy aligned with your From domain, one-click unsubscribe, unsubscribes honored within two days, complaints under 0.3% |
| Outlook.com | Domains sending more than 5,000 messages a day to Outlook.com, Hotmail and Live addresses | SPF and DKIM passing, DMARC of at least p=none aligned with SPF or DKIM |
Three details catch newsletters out. Gmail counts every message from the same primary domain together, so a newsletter and a marketing subdomain add up. Once Gmail classes you as a bulk sender, that status is permanent. And Microsoft rejects non-compliant mail outright with a 550 5.7.515 error rather than quietly filing it in junk.
Every sender, bulk or not, still needs SPF or DKIM, valid forward and reverse DNS on the sending IPs, TLS, and a spam rate under 0.3% at Gmail. If your list is small, set up the bulk rules anyway. It costs an afternoon, and you will not have to scramble when you cross the line.
The setup order
Order matters. Turning on DMARC enforcement before every sender is authenticated is how newsletters block their own invoices and password resets.
- List every service that sends as your domain. Your newsletter platform, your billing tool, your CRM, your help desk, your own inbox.
- Pick the sending domain. Decide whether the newsletter sends from your main domain or a dedicated subdomain, and keep cold outreach on a separate domain entirely.
- Publish SPF covering the services that need it.
- Publish DKIM keys for each service, signing with your domain rather than the vendor's.
- Publish DMARC at p=none with a reporting address, and read the reports for a few weeks.
- Add one-click unsubscribe headers and a visible unsubscribe link.
- Register the domain in Google Postmaster Tools and Microsoft SNDS before you need them.
- Warm up the domain or platform with your most engaged readers first.
- Move DMARC to quarantine, then reject, once the reports show all of your legitimate mail passing.
- Add BIMI if you want your logo in the inbox.
Authentication: prove the mail is really yours
SPF
A DNS TXT record listing the services allowed to send mail for your domain. You get one SPF record per domain, and it can trigger at most ten DNS lookups. Every vendor that tells you to add an include uses part of that budget.
How to check it: send a test to a Gmail address, open the message menu and choose Show original. SPF should read PASS. If you have more than one SPF record, or too many lookups, it fails for everyone.
DKIM
A cryptographic signature on every message, with the public key published in DNS. Use 2048-bit keys where your provider supports them. The signature should use your domain, not your platform's shared domain, or it will not align for DMARC.
How to check it: in Show original, DKIM should read PASS with your domain next to it. If you see the platform's domain instead, custom DKIM is not set up yet.
DMARC
A policy telling mailbox providers what to do with mail that fails, and where to send reports. DMARC only passes when SPF or DKIM passes and matches the domain in your From address. That alignment is the part most setups miss.
Start at p=none with a rua reporting address. The reports show every server sending as your domain. Fix the legitimate ones, then move to p=quarantine and finally p=reject.
How to check it: Show original should list DMARC as PASS. Read the aggregate reports weekly while you are still at p=none. A report parser saves hours, because the raw files are XML.
BIMI
BIMI shows your logo beside your messages in supporting inboxes, including Gmail, Yahoo and Apple Mail. It requires DMARC at enforcement: quarantine or reject, applied to all of your mail. Gmail does not support it at p=none.
You also need a certificate. A Verified Mark Certificate (VMC) requires a registered trademark for the logo, and Gmail shows a checkmark next to VMC senders. A Common Mark Certificate (CMC) needs no trademark and is accepted by Gmail, but not every inbox supports it. The logo itself is a square SVG in the restricted SVG Tiny format.
How to check it: run the domain through a BIMI record checker, then confirm the logo appears on a real message in Gmail.
Unsubscribes: make leaving easy
A reader who cannot find the exit presses Report spam instead. That costs you far more than an unsubscribe.
- Send a List-Unsubscribe header with an HTTPS link, plus a List-Unsubscribe-Post header for one-click unsubscribe as defined in RFC 8058. Both headers must be covered by your DKIM signature.
- Your endpoint must accept the POST and unsubscribe the reader with no login and no confirmation page.
- Keep a visible unsubscribe link in the footer too.
- Process unsubscribes within 48 hours. Immediately is better.
How to check it: open a test send in Gmail. An Unsubscribe link should appear next to the sender name. Click it, and confirm the address is suppressed in your platform before the next send.
Warm-up: earn trust before volume
Mailbox providers judge a new domain or IP by its first weeks. A brand new domain that suddenly sends to your whole list looks like a spammer, whatever the content.
- Start with readers who opened or clicked recently. Their engagement builds reputation fastest.
- Increase volume step by step over a few weeks, not all at once.
- Watch bounces, complaints and deferrals after every step. If they rise, hold the volume where it is until they settle.
- Keep the schedule, from name and template the same as before. Change one thing at a time.
- If you are migrating platforms, keep the old platform live until the new one is fully warmed.
On a shared IP, your platform's reputation carries you while your domain builds its own. A dedicated IP only makes sense when you send enough volume to keep it warm.
List hygiene and a sunset policy
- Remove hard bounces immediately and suppress repeat soft bounces.
- Remove anyone who marks you as spam, automatically.
- Confirm new signups, or at least validate addresses at the form, to keep typos and bots out.
- Never import purchased or scraped lists.
- Run a sunset policy for readers who stopped engaging.
A sunset policy is simple. Pick a window that suits your frequency. A three-times-a-week newsletter sees engagement fade faster than a monthly one. When a reader passes it, send a short re-engagement email asking if they still want the newsletter. If they do not click, stop sending.
Deleting readers feels like shrinking. It is the opposite. Inactive addresses drag down engagement, and some old ones get recycled into spam traps.
Base the policy on clicks and replies, not opens alone. Opens are the least reliable signal you have.
Sending habits
- Send from a consistent domain and from name on a predictable schedule.
- Keep sponsor outreach and other cold email on a separate domain from your newsletter.
- Use your own domain for tracked links where your platform allows it, so links match the sender.
- Keep the HTML lean and include a plain-text version.
- Screen subject lines and copy for spam-trigger wording before scheduling.
Measure what matters
Watch bounce and complaint rates on every send, along with inbox placement on the major providers. In Google Postmaster Tools, Gmail asks you to keep the user-reported spam rate under 0.1% and never reach 0.3%. Postmaster Tools also has a compliance status dashboard that marks each sender requirement as compliant or needing work.
Open rates need care. Apple's Mail Privacy Protection downloads remote content, including tracking pixels, in the background when a message arrives, whether or not the reader opens it. For many lists that means a large share of recorded opens are machine loads.
Clicks need care too. Corporate security scanners follow links to check them before the reader sees the message. For business audiences, raw clicks can be far higher than real reading.
Monitoring cadence
Every send
- Bounce rate and complaint rate, compared with your usual range.
- Deferrals and rejections by mailbox provider.
- Unsubscribes processed and suppressed.
Weekly
- Google Postmaster Tools spam rate and compliance status.
- DMARC aggregate reports for unknown senders.
- Human clicks after bot filtering, by provider.
Monthly
- A seed or inbox placement test across Gmail, Outlook and Yahoo.
- Blocklist checks for your domain and sending IPs.
- Run the sunset policy and review what it removed.
Quarterly
- Audit DNS: who can send as your domain, and is every one still needed?
- Review DMARC policy and certificate expiry dates for BIMI.
When things go wrong
Opens dropped sharply overnight
It is 9 a.m. on send day and opens are half of last week's. Do not rewrite subject lines yet. Check the delivery data first.
- Split opens by mailbox provider. A drop at one provider points to a placement problem there.
- Check bounces and deferrals for that send.
- Send a test and confirm SPF, DKIM and DMARC still pass. A DNS change elsewhere in the company can break them silently.
- Ask what changed: a new link domain, a new template, a new segment, a big import.
Gmail is sending you to spam
- Check the spam rate and compliance status in Postmaster Tools.
- Narrow the next sends to your most engaged readers, and widen again as placement recovers.
- Make unsubscribing easier, not harder.
- Look for a recent spike: a cold import, a giveaway signup flood, or a much higher send frequency.
Recovery takes weeks of clean sending. There is no form that fixes reputation faster.
You landed on a blocklist
- Confirm which list and whether it covers your domain or your sending IP.
- On a shared IP, tell your platform. They manage the IP.
- Find the cause first, usually a bad import or a spam trap hit, then fix it.
- Request removal through the list's own process. Most delist quickly once the cause is gone.
Outlook is rejecting mail
A 550 5.7.515 bounce from Outlook.com means your domain failed its authentication requirements. Check SPF, DKIM and DMARC alignment for the exact domain in your From line, fix the record, and resend to those readers.
What most guides miss
Lessons from systems we have built and run, not the usual checklist.
Security scanners inflate B2B engagement
Corporate email security tools often open and click links before a person does. For business audiences, raw open and click rates can be far higher than real reading. Filter out machine activity before you judge a send or report to sponsors.
The tells are consistent: clicks within seconds of delivery, every link in the issue clicked at once, or clicks from data center addresses. Filter on those and keep the raw numbers alongside, so you can explain the gap.
Opens are a weaker signal than they used to be
Privacy features in some mail apps load images automatically, which records opens that never happened. Weight clicks, replies and conversions more heavily.
Do not let your webhooks drop events
If you track delivery and engagement events yourself, a busy send produces a burst of them at once. Make sure your system can absorb that spike, or your bounce handling and reporting will quietly miss data.
A missed bounce event is worse than a missed click. The address stays on the list, bounces again next send, and your bounce rate creeps up with no obvious cause.
Be careful with aggressive bot filters
Filters that flag signups or readers as bots can catch real people too. Review what they remove before deleting anyone for good.
Your newsletter shares a reputation with the rest of the company
Billing emails, sales sequences and the newsletter often send as the same domain. One bad cold campaign can hurt the issue readers actually want. Separate the streams before you need to.
How we do it
We set up authentication, one-click unsubscribe, automatic bounce and complaint handling, and monitoring as part of every system we build. For a B2B trade newsletter that moved from Beehiiv to its own Resend setup, that meant domain authentication, webhook-driven suppression of bounces and complaints and bot-click filtering on engagement data. See operations, our Resend infrastructure work, and the guide to migrating without losing deliverability.
Sources
- Gmail Help: Email sender guidelines
- Yahoo Sender Hub: Sender best practices
- Microsoft Tech Community: Outlook's new requirements for high-volume senders
- Gmail Help: Email sender guidelines FAQ
- RFC 7208: Sender Policy Framework (SPF)
- RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
- RFC 9989: Domain-based Message Authentication, Reporting, and Conformance (DMARC)
- RFC 8058: Signaling one-click functionality for list email headers
- Gmail Help: Postmaster Tools dashboards
- Microsoft: Smart Network Data Services (SNDS)
- Google Workspace Admin Help: Set up BIMI
- Apple: Mail Privacy Protection and privacy
Facts checked against these sources in October 2026.