How to Improve Newsletter Deliverability in 2026 (After the Rules Changed)

You spend two days building a newsletter. Good copy, clean design, a list of 8,000 people who asked to hear from you. You hit send.

And a third of them never see it.

No bounce, no error, no warning. The email was “delivered.” It just landed in spam, or the Promotions tab, or some quiet folder nobody opens. If you’ve felt that specific frustration, the wail of why is this happening, you’re in the right place.

Here’s the thing most guides won’t tell you: the rules for getting a newsletter into the inbox changed hard in 2024 and 2025. A lot of the advice still floating around (including, until recently, the advice on this very page) is years out of date. What actually moves the needle now, from someone who’s published the DNS records and watched the numbers move.

The short version

If you only read the bold bits, read these:

• “Delivered” doesn’t mean “in the inbox.” Your real number is inbox placement, and your open rate can’t be trusted to tell you what it used to.
• If you send more than 5,000 messages a day to Gmail or Yahoo, you must have SPF, DKIM, and a DMARC policy, a one-click unsubscribe, and a spam-complaint rate under 0.3%. This isn’t optional anymore. Microsoft added its own version in 2025.
• Authentication is table stakes, but your list is the lever almost nobody pulls. Hygiene and engagement beat every clever trick.
• The “avoid spam trigger words” advice is mostly a myth. Stop worrying about the word “free.” Start worrying about who’s opening your mail.
• Send on a steady cadence. Spikes look like spam.

Now the detail.

“Delivered” is not the same as “in the inbox”

Two words get used as if they mean the same thing, and the gap between them is where newsletters go to die.

Email delivery means the receiving server accepted your message. That’s it. It said “yes, I’ll take this.” It did not promise to show it to a human.

Email deliverability means the message actually reached the inbox, not the spam folder, not a filtered-away tab. This is the number that matters, and it has a name: inbox placement rate (IPR).

Plenty of senders look at a 98% delivery rate and feel great. But if a big slice of that 98% got quietly routed to spam, the dashboard is flattering you. The server accepted the file. Nobody read it.

And here’s the part that trips up even experienced marketers in 2026: your open rate is no longer a clean signal. Since Apple rolled out Mail Privacy Protection in September 2021, Apple Mail pre-loads images for users who turn it on, which fires your open-tracking pixel whether or not a human looked at anything. Depending on how much of your list is on Apple Mail, a chunk of your “opens” are robots. So if you’ve been steering your whole program by open rate, you’ve been steering by a fogged-up windshield. Lean on clicks, replies, conversions, spam complaints, and bounces instead. Those still mean something.

The 2024-2025 rules you can’t sidestep

This is the section the old guides are missing, and it’s the one that decides whether your newsletter even gets a fair hearing.

In February 2024, Google and Yahoo started enforcing a shared set of requirements for bulk senders, which they define as anyone sending more than 5,000 messages a day to their domains. Microsoft followed with its own high-volume sender requirements in 2025. The three biggest mailbox providers on earth now agree on the basics, and “we’ll get to it later” is no longer a strategy.

Here’s what they require, in plain terms:

1. Authenticate everything. SPF and DKIM on your sending domain, plus a DMARC policy published in DNS. A policy of p=none is enough to meet the bar, but it has to exist and align. (More on each of these in the next section.)

2. Align your “From” domain. The domain in your visible “From” address has to match the domain that passes SPF or DKIM. Sending your newsletter “from” your brand but authenticating under some other domain breaks alignment, and breaks delivery.

3. One-click unsubscribe, honored fast. You need the List-Unsubscribe header and List-Unsubscribe-Post, so a recipient can opt out in a single tap without leaving their inbox. And you have to action it within two days. A buried unsubscribe link at the bottom of the email no longer satisfies the requirement on its own. (SMTP2GO handles these headers for you; here’s how the one-click unsubscribe header works and the wider unsubscribe best practices.)

4. Keep spam complaints low. Stay under 0.3%, and treat 0.1% as your real target. Cross 0.3% consistently and providers will start routing you to spam wholesale. For a 10,000-person send, 0.3% is 30 complaints. That’s a small number. It adds up faster than you’d think when you email people who forgot they signed up.

We wrote up the specifics when they landed: Gmail and Yahoo’s 2024 inbox protection rules, and the changes to Microsoft Outlook’s filtering.

One honest caveat. If you send under 5,000 a day, the providers don’t formally require all of this yet. Do it anyway. Every one of these is just good sending, the thresholds only mark where it stops being a suggestion, and senders who wait until they’re forced tend to get caught mid-growth with a cold domain and no DMARC. Ask me how I know.

Authenticate your domain properly (and watch it actually work)

Three records do the heavy lifting. You don’t need to become a DNS expert, but you do need all three set up right.

SPF (Sender Policy Framework) lists which servers are allowed to send mail for your domain. When SMTP2GO sends your newsletter, the receiving server checks your SPF record to confirm we’re on the guest list. Here’s the full walkthrough on building an SPF record.

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to every message, so the receiver can confirm the email wasn’t tampered with in transit and genuinely came from you. This is the one people most often skip or fumble. The DKIM deep dive covers it properly.

DMARC sits on top of SPF and DKIM and tells receivers what to do when a message fails: nothing (p=none), send to spam (p=quarantine), or reject outright (p=reject). It also stops bad actors from spoofing your domain. Start at p=none to monitor, then tighten. What DMARC is and how to set it.

Your list is the lever almost nobody pulls

Here’s what most people miss. You can authenticate flawlessly and still land in spam, because authentication only proves you’re you. It doesn’t prove you’re wanted. Mailbox providers decide that by watching how people treat your mail. And the rawest input to that is the quality of your list.

Clean it, regularly. Every send to a dead address, a typo, or someone who hasn’t opened in a year drags your reputation down. Pull invalid and long-dead addresses out. Why list scrubbing matters and how to do it.

Use suppression lists, not guesswork. When someone hard-bounces or unsubscribes, they should never get mailed again, automatically. SMTP2GO suppresses those for you so a stale address doesn’t quietly poison your next campaign. How suppressions work.

Watch out for spam traps. These are addresses that exist only to catch sloppy senders. Recycled traps are old real addresses providers have repurposed, which is why mailing people who went silent two years ago is genuinely dangerous. Pristine traps were never real and only show up on lists you bought, scraped, or guessed at. Which is the short version of: never buy a list. Ever.

Sunset the silent ones. If a subscriber hasn’t opened or clicked in months, don’t keep hammering them. Move them to a re-engagement flow, give them one clear chance to stay, and if they don’t take it, let them go. A smaller engaged list out-delivers a big numb one every single time.

Double opt-in earns its keep. Asking new subscribers to confirm via a click filters out typos, bots, and people who’ll forget they signed up and hit “spam” later.

JWK Solicitors came to SMTP2GO after their domain landed on a blocklist, the kind of mess that’s usually a list-hygiene problem underneath. Once they were sending clean through a reputable relay, the issues stopped. If you’re already on a blocklist, here’s how to get off one.

Cadence and warm-up: steady beats spiky

Newsletters have a sending-pattern problem the one-off-campaign crowd doesn’t think about. You send to a big list, on a schedule, over and over. Mailbox providers love consistency and distrust sudden change.

If you’re sending from a brand-new domain or a fresh dedicated IP, you can’t just blast your whole list on day one. You warm up: start small, grow volume gradually over days or weeks, and let providers build trust as the engagement data comes in. Ramp too fast and you’ll trip filters that exist specifically to catch spammers, who love a fresh IP and a huge first send. Our high-volume warm-up guide walks the schedule. If you’re weighing your own IP against a shared pool, dedicated vs shared lays out the trade-off.

Once you’re warm, hold a rhythm. If your newsletter goes out Tuesdays, keep it Tuesdays. Don’t go quiet for three months and then dump six emails in a week to “make up for it.” That pattern reads as exactly what providers are built to block.

Group IMD is the example I point people to here. As a SaaS provider, they scaled with SMTP2GO from 10,000 emails a month to over a million across six years, and the thing that made that possible wasn’t a trick. It was steady, reliable sending that let their reputation grow with their volume instead of fighting it.

Content that actually helps (and the myth that doesn’t)

Let’s kill a zombie. The old advice, including the advice that used to live on this page, said to avoid “spam trigger words” like free, buy now, winner. There were whole lists of forbidden words.

Mostly a myth. Modern filters don’t run a word blocklist. They weigh reputation, authentication, and engagement. A sender in good standing can write “free” in a subject line and sail into the inbox. A sender with a trashed reputation will hit spam writing about quarterly accounting. The word was never the problem.

What does help your content land and get read:

• Design for the phone. Most newsletters get opened on mobile. One-column layout, readable font size, tappable buttons in the middle of the screen. Optimizing emails for mobile.
• Never ship image-only. An email that’s one big image with no real text looks like classic spam to a filter, and breaks completely for anyone with images off. Balance image and text, and always add alt text so the message survives when images don’t load.
• Keep links clean and few. Show readable link text, not a raw https://... string, and skip URL shorteners, which filters distrust because spammers lean on them. Here’s the case against shorteners in email.
• Write subject lines for humans, not filters. Short, honest, specific. The thing that hurts you isn’t a “spammy word,” it’s a misleading subject that earns a spam complaint when the body doesn’t deliver.

So yes, content matters. Just not in the superstitious way the old lists implied.

Test before you send (the modern way)

A real pre-send test in 2026 does three things. It runs your message past a seed list across Gmail, Yahoo, and Outlook to see where it actually lands (inbox, tab, or spam) at each provider, because your Gmail placement and your Outlook placement can be completely different. It confirms your authentication passes (SPF, DKIM, DMARC aligned). And it renders your email across the clients your audience actually uses, so a broken layout doesn’t tank engagement and, downstream, deliverability.

One honest limit worth knowing: seed tests are a proxy. Seed addresses don’t open, click, or reply, and real human engagement is the single biggest factor providers weigh. So use seed testing to catch the obvious problems before a send, then watch your real per-provider numbers (clicks, complaints, bounces) afterward to see the truth. SMTP2GO’s email testing is built for exactly this loop.

Pick infrastructure that does the boring stuff right

Now the honest part, and the part I can be honest about precisely because SMTP2GO isn’t trying to be your newsletter design tool.

If what you need is drag-and-drop campaign design, visual audience segments, and a built-in template gallery, you want a marketing platform, and you should use one. SMTP2GO sits a layer beneath that: the sending engine that gets the mail delivered, whether your newsletter comes out of a marketing tool, a CMS, a CRM, or your own code. Plenty of senders run their campaign tool on top and route the actual delivery through SMTP2GO underneath, because the design layer and the deliverability layer are different jobs.

What that engine is doing for your newsletter, quietly:

• Reputation management and inbox placement as a full-time concern, not an afterthought, including the per-provider monitoring you’d otherwise do by hand.
• Authentication, suppressions, and the unsubscribe headers handled so you meet the 2024-2025 requirements without hand-rolling DNS and compliance plumbing.
• Clear reporting that shows delivered vs. bounced vs. spam-complained, so when something’s off you can see it instead of guessing.
• Flexible ports (including 2525) so the send works on networks that block the usual ones.
• 24/7 human support out of New Zealand, plus ISO 27001 certification, GDPR compliance, and M3AAWG membership, which is the deliverability industry’s standards body, not a logo we bought.

The support point isn’t fluff, it’s why people switch. ThinkPorch moved to SMTP2GO after AWS SES took too long resolving an issue, and the thing they flagged wasn’t features, it was getting a real answer fast. StoredTech has run phone systems, copiers, and other devices through SMTP2GO since 2011 with, in their words, no headaches and no downtime. GlaxoSmithKline uses it for time-critical manufacturing notifications where a late email stalls a production line, and it worked accurately from day one. Different senders, same underlying need: the mail has to arrive.

That’s the trade. Bring your favorite tools for building the newsletter. Let infrastructure that does deliverability all day handle getting it there.

Your pre-send checklist

Tape this near your monitor. Before any newsletter goes out:

• [  ] SPF, DKIM, and DMARC published and passing, with the From domain aligned
• [  ] One-click List-Unsubscribe header present and working
• [  ] List scrubbed: invalids removed, hard-bounces and unsubscribes suppressed
• [  ] Silent subscribers sunset or moved to re-engagement, not mailed blindly
• [  ] Sending on your normal cadence (no surprise spikes; new domain warmed up)
• [  ] Mobile-friendly layout, real text (not image-only), alt text on images
• [  ] Links clean and readable, no URL shorteners
• [  ] Seed-tested across Gmail, Yahoo, and Outlook; rendering checked
• [  ] Spam-complaint rate trending under 0.1%, comfortably below 0.3%

Get those right and you’re not hoping your newsletter lands. You’ve stacked the odds.

About the author

Simon Slade

Co-Founder at SMTP2GO • Website

Simon is a co-founder of SMTP2GO, launched in 2006 out of Christchurch, New Zealand. The idea was simple: a reliable way to send email from anywhere, even when local networks were blocking the usual ports. Twenty years on, SMTP2GO delivers for 35,000+ businesses across 130+ countries. SMTP2GO is ISO 27001 certified, GDPR compliant, an M3AAWG member, and a five-time Deloitte Technology Fast 500 company.