Key takeaway
"Email marketing bloggers" splits in two: the people who publish about email, and the bloggers who send it. The reading lists cover the first and rank them flat. Sort by layer instead. The mailbox providers, the IETF and M3AAWG publish what a sender is required to do, and everybody else is interpreting that. The oldest list still ranking was written in 2016, which says how much of the genre is recycled. I read layer one for facts and layer two for judgment.
What this search actually turns up.
"Email marketing bloggers" covers two different groups of people, and a search for the phrase returns both at once: the writers who publish about email, and the bloggers who use email to reach their own readers. The reading lists that dominate the results all answer the first reading, and every one of them is a list of interpreters, which means the useful question isn't which blog you picked but which layer of the subject you're reading. The lists themselves say a lot about that: they usually run to fifteen entries, they're almost entirely software companies' own content marketing, the publisher's own blog is usually somewhere on the list, and the oldest one still ranking was written in 2016.
That 2016 page is also the only list still ranking that names actual people rather than companies, which tells you how little the format has moved. Sort by name and you get a taste ranking. Sort by what a piece of writing is for and you get something you can act on.
The reading list stops being useful as an idea right there. A list of publishers tells you where to go looking, and it tells you nothing about what has to reach you whether you go looking or not. I've spent a decade building email platforms, and the reading that ever changed what we shipped was never the roundup.
The writers and publications worth reading.
The seven below are sorted by what each one is for rather than ranked, because a ranking of blogs is a ranking of taste and yours is as good as mine. Some of them are software companies and some are individuals working under their own name, and both are worth reading for different reasons: a company writes from a vantage point you don't have, a person writes from a decade of being wrong in public and then correcting it.
- Chad S. White: author of four editions of Email Marketing Rules, which is the closest thing the discipline has to a written rulebook of practice.
- Kath Pay: founder of Holistic Email Marketing and author of Holistic Email Marketing, on treating a program as one customer journey rather than a stack of campaigns.
- Jordie van Rijn: the independent consultant behind EmailMonday and EmailVendorSelection, and strong on how the vendor landscape is actually laid out.
- Ann Handley: MarketingProfs, the author of Everybody Writes, and her own newsletter, which is the one to read on how a subscription should sound.
- Joanna Wiebe: Copyhackers, and the conversion copywriting that most email teams are quoting secondhand without knowing where it came from.
- Litmus: rendering, testing, and how mail actually behaves in the clients people read it in.
- Really Good Emails: a searchable library of real sends, which beats any list of principles on the days you're stuck on what an email should look like.
Every name there is somebody's judgment, including on the days they flatly disagree with each other, which is the point of reading more than one. It's also the limit. None of them can tell you what a mailbox provider has decided to require of you this year, because that isn't theirs to decide.
The documents that are not opinion.
A small number of publishers put out documents that describe what senders are required to do, rather than what somebody thinks works. They aren't blogs, they don't have a house style, and they're the layer everything in the previous section is an interpretation of. Read them first. An interpretation you read without the source is somebody else's summary of your own obligations, and the summary is always shorter than the thing it summarizes for reasons that suit the summarizer.
- Google's sender guidelines: what Gmail requires of anyone sending more than 5,000 messages a day to Gmail accounts, in force since 1 February 2024, with SPF and DKIM authentication on the sending domain, a published DMARC policy, and a spam rate below 0.30%.
- Yahoo's sender best practices: the same shape with its own numbers, enforced from February 2024, and the document that spells out a valid DMARC policy, a spam rate below 0.3%, and a two-day window for acting on unsubscribes.
- RFC 8058: the standard from January 2017 that defines
List-Unsubscribe-Post, the header behind the one-click unsubscribe button both providers now expect. - M3AAWG's published documents: the industry forum where mailbox providers and senders write down sender practices together, with a Sender Best Common Practices document that's revised as the rules move.
These set a floor and nothing more. They say what gets you delivered, never what's worth sending, which is the entire reason the writers in the last section have jobs. What they also are, though, is machine-readable: published at a stable address, versioned, and specific enough to check something against. That's the difference between an email stack an agent can operate and one where every rule that governs your sending lives in somebody's blog post from March.
What a platform's blog is genuinely good for.
Most of the reading lists on this search are lists of software companies' blogs, and that isn't a criticism by itself. A vendor blog is at its strongest on the things that vendor can see and you can't. Litmus can tell you how a template renders across mail clients because rendering them at scale is its whole business. A sending platform can describe aggregate delivery behavior across thousands of senders, which no single sender can observe from inside one account. Any product team can explain the mechanics of its own product better than a bystander can.
The weak spot is narrow and predictable, and it's the question of which product to use. A list of the best email platforms published by an email platform tends to have that platform on it, usually somewhere near the top. That's true of almost every roundup on this search, ours included when we write one.
So the filter is simple enough to hold in your head. Read a vendor blog for mechanism, read a practitioner for judgment, and don't swap the two around. The vendor knows how the machine behaves; the practitioner has had to live with the consequences of a decision the machine made easy.
If you came here as a blogger with a list to build.
The other half of this search is people with a blog and an email list, and the honest starting point is that a blog with a newsletter is a sender. That word matters more than it sounds like it should. The moment your list crosses into bulk volume you're inside the same requirements those four documents set, whatever the blog is about, and nobody makes an exception for a personal site with good writing on it.
The decisions that turn out to matter aren't the tooling ones, which is the opposite of what most of the results here will tell you. They're whether the list is a subscription or an announcement channel, because those are two different promises and readers can tell which one they got. They're what the reader actually agreed to when they typed their address in. They're whether the archive is worth anything to somebody who arrives two years later, which decides whether the list compounds or just churns. I've seen what a compounding list is worth in practice: Fridja sold a quarter of its stock before the store even opened, off nothing more than early access to its list.
The criteria worth stating here: what a sender owes once volume goes bulk, whether the list is genuinely yours to export, and what the exit looks like on the day you want one. For our part, Nitrosend specializes in email and sits under whatever publishes the blog, as the sending layer rather than the site or the archive. Contacts are unlimited on every plan including Free, and every capability is an API endpoint and an MCP tool before it's a screen. The order is the whole point, because an agent pointed at a product whose primitives are screens can only click the screens.
A reading routine that survives a real week.
Nobody keeps up with fifteen blogs. A reading list built on the assumption that you will is a list you abandon in a fortnight, usually with a folder of unread newsletters as a monument to the attempt. The way out is to stop sorting by quality and start sorting by consequence: what happens if you miss this? Miss a good essay on segmentation and you read it in April instead. Miss a change to what a mailbox provider requires and your mail stops arriving. Three rules follow from that, and they're the whole routine.
- Subscribe to the rule sources directly, because missing a sender requirement costs you delivery and no summary of it arrives on a schedule you control.
- Pick two practitioners and read them properly, which is worth considerably more than skimming ten and retaining none.
- Keep one library of real sends for the days when you're stuck on execution rather than on strategy.
Even done well, a routine is still a person reading, and I'd rather not stake delivery on my own attention in a bad week. The half of this with consequences shouldn't depend on someone remembering it. An operator running email through an agent wants the sending rules checked against what's actually going out, at the moment it goes out, rather than recalled from a post they read in February.
The reading is somebody else's judgment and it's worth having. The requirements aren't judgment at all, and they're the half you shouldn't be carrying in your head. A platform built for humans clicking buttons can't check a sender requirement at the moment a message goes out, whatever agent is bolted to the front of it.
Nitrosend is an AI-native email platform, and it runs your whole email stack from one agent command, so the rules sit where the sending happens rather than in a bookmark folder. Start on the free tier and put something real through it: 8,000 emails to begin with, then 500 a month, unlimited contacts, and full MCP, API, and CLI access with no card.
Sources
- Google, Email sender guidelines: the bulk-sender threshold of more than 5,000 messages a day to Gmail accounts, the 1 February 2024 date, the SPF and DKIM authentication and published DMARC policy required of bulk senders, and the 0.30% spam-rate ceiling.
- Yahoo, Sender best practices: enforcement from February 2024, the DMARC policy requirement, the 0.3% spam rate, and the two-day window for acting on an unsubscribe.
- RFC 8058: Signaling One-Click Functionality for List Email Headers, January 2017, the standard that defines
List-Unsubscribe-Post. - M3AAWG, published documents: the industry forum's document library, including the Sender Best Common Practices it revises as sender requirements change.
Common questions
Split them by what they're for. Litmus is strong on rendering and testing, and Really Good Emails keeps a searchable library of real sends for when you're stuck on execution. For judgment rather than mechanism, read Chad S. White, Kath Pay, and Jordie van Rijn, who have each been writing about email for long enough to have changed their minds in public.
Judge by body of work rather than by job title, because the title is the part that rots first. Chad S. White wrote four editions of Email Marketing Rules, Kath Pay wrote Holistic Email Marketing, Joanna Wiebe built Copyhackers, and Ann Handley wrote Everybody Writes. Each is worth following on a specific subject rather than on email in general.
It's the convention that roughly four in five of your sends should give the reader something and one in five should ask for something. Treat it as a rule of thumb people quote rather than as a measured split, because nothing enforces it and no mailbox provider counts it. What the reader agreed to when they subscribed matters far more than the ratio.
It's the one channel where the audience is a list you hold rather than an account somebody else ranks, which is the whole case for it and hasn't changed. The cost is that you're a sender, so the requirements the mailbox providers publish apply to you: authentication on every message, a spam rate under their ceiling, and a working one-click unsubscribe.
In four places. <a href="https://support.google.com/mail/answer/81126" rel="nofollow noopener">Google's sender guidelines</a> and Yahoo's sender best practices set what each provider requires of a bulk sender. RFC 8058 defines the header behind one-click unsubscribe. M3AAWG publishes the industry's Sender Best Common Practices. Everything else you'll read about sender requirements is an interpretation of those.
It's a count of messages a day to one provider, not a count of subscribers. Google's threshold is more than 5,000 messages a day to Gmail accounts, so what decides it is how many of your readers are on Gmail and how often you send to them, rather than how big the list looks in your dashboard. The sensible move is to meet the requirements well before you're near the line, since authentication and a working one-click unsubscribe are worth having at any volume.
Choose on three criteria rather than on a feature list. What the tool does for you once your volume crosses into bulk and the sender requirements apply. Whether the list is genuinely yours to export on any day you ask. And what the exit looks like, including whether your archive and your subscriber history come with you when you leave.
Yes, and it's worth knowing what free usually means: a send allowance rather than a contact allowance, so the bill arrives when your volume grows rather than when your list does. Nitrosend's free tier is 8,000 emails to start, then 500 a month, with unlimited contacts and full MCP, API, and CLI access, and no card.