惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
人人都是产品经理
人人都是产品经理
Cisco Talos Blog
Cisco Talos Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
V
V2EX
博客园 - 三生石上(FineUI控件)
Martin Fowler
Martin Fowler
WordPress大学
WordPress大学
D
Docker
S
SegmentFault 最新的问题
博客园 - 聂微东
美团技术团队
Apple Machine Learning Research
Apple Machine Learning Research
月光博客
月光博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Last Week in AI
Last Week in AI
M
MIT News - Artificial intelligence
F
Fortinet All Blogs
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The GitHub Blog
The GitHub Blog
GbyAI
GbyAI
L
LangChain Blog
Vercel News
Vercel News
博客园 - 叶小钗
MongoDB | Blog
MongoDB | Blog
Stack Overflow Blog
Stack Overflow Blog
H
Help Net Security
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Cloudflare Blog
Engineering at Meta
Engineering at Meta
T
Threat Research - Cisco Blogs
T
Threatpost
Scott Helme
Scott Helme
T
Tailwind CSS Blog
Latest news
Latest news
Stack Overflow Blog
Stack Overflow Blog
Blog — PlanetScale
Blog — PlanetScale
The Register - Security
The Register - Security
罗磊的独立博客
P
Proofpoint News Feed
腾讯CDC
S
Schneier on Security
雷峰网
雷峰网
A
About on SuperTechFans
T
Tenable Blog
F
Full Disclosure
Cyberwarzone
Cyberwarzone
博客园_首页
有赞技术团队
有赞技术团队
K
Kaspersky official blog

文章列表

Compulsive curiosity, or, how I built an infinite idea machine Gift details on the subscriber portal Portal link in the archive nav The physicists who convinced Fermilab to send Brazil's emails First, add no friction: How micropayments lost and subscriptions won Filter subscribers and automations by source Automations, rebuilt What email will look like in the future Filter subscribers by bounce date and reason Email could have been X.400 times better Three features are moving behind the paywall Firewall changes and improvements Put your name and voice into your company newsletter Simplified email address settings Subscription wall Inboxes were overwhelming before we'd even named them The US government tried really hard to screw up email Public postmortem: database connection exhaustion Ask a nerd: what is the best way to unsubscribe from newsletters? Bookshop.org embeds Email was into agents before they were cool Passwordless login Rename metadata keys in bulk A spring cleaning for our legal docs Ask a nerd: what happens when you click the spam button? Passkey support for two-factor authentication How Buttondown's API versioning works Safer defaults for the email creation API How to send email to space How we enabled Content Security Policy for everyone Recovery codes for two-factor authentication Filter sent emails by engagement rate How we migrated to TypeIDs without breaking clients How we check every link in your email Use newsletter metadata in your emails Should we bring back email exploders? Sort and filter by open and click rates Custom click tracking domains More newsletter settings in the API Revamped replies Custom email templates for everyone Simplified cancellation Ask a Nerd: Does email length affect deliverability? The changelog, reborn Swedish localization Forwarding an email is not always straightforward Public descriptions for tags OpenAPI spec for archives How Rodrigo brings a humanistic view to consumer technology Your newsletter's archives are more valuable than your list Survey responses on the web How Brandon Lucas Green shares his music and supports artists Subscribers can come from anywhere. Even another newsletter platform's form. Better tag self-management Smarter automation filters Granular API keys Ask A Nerd: How does newsletter cadence affect deliverability? New design settings pages Snippets Starred views More ways to customize your archives Inbox filtering Mastodon follower analytics Ask a Nerd: What are good open, click, and response rates for an email newsletter? How we migrated our database to PlanetScale Two new archive themes Ask a Nerd: Does attaching files to your newsletter hurt deliverability? Custom buttons now work in Markdown mode Seline and Tinylytics support Unban subscribers Announcement bars for your archives Public postmortem: archive downtime Bang paths, source routing, and how email trips were planned 2025 disposables.app Russian localization Ask a Nerd: Can you improve email deliverability with a personal domain? More locale options How we interview customers at Buttondown Bluesky analytics Minimum viable complexity Reply to conversations How Jeffery Hicks goes behind-the-scenes in his newsletter Changes to our stack in 2025 2026: Emails Randomize survey answer order TK reminders in the editor What the hell is a UTM? Why we insourced analytics Scroll sync in the editor 2026: Archives How Kelly Jensen uses Buttondown to discuss key library issues How Jamie Thingelstad uses Buttondown to explore tech topics Keeping feature creep at bay Improved filters Content Security Policy in archives Open source Sniperl.ink Auto-activating RSS reader subscriptions What the hell is ActivityPub? Gift subscriptions
How we keep deliverability high
Justin Duke · 2023-11-02 · via

TL;DR

Everything we do comes down to three things:

  1. Make sure the only people getting your newsletter are the ones who actually want to get your newsletter.
  2. Make sure the emails being sent out are content-rich, accessible, and performant.
  3. Be deliberate and careful in who we allow onto the platform to make sure our reputation stays golden.

There's no secret sauce — it's not rocket science. It's just diligence and good engineering. But for the details, keep reading!

Mandatory double opt-in

Some email platforms treat double opt-in as a "table stakes" feature that authors can turn on and off as they wish, or even treat cold emailing (the practice of sending emails in bulk to addresses who haven't given you permission to do so) as legitimate.

Buttondown... does not. Every single subscriber on Buttondown must explicitly opt into your newsletter. This keeps the risk of spam complaints low, your engagement high, and readers everywhere happy.

That being said, we're nothing if not flexible and hospitable to other use cases. If you're confirming double opt-in outside of Buttondown (for instance, asking authors to confirm their interest as part of a registration or checkout flow) you can always email us and we can discuss other options!

Automatic clean-up

Even if a subscriber to your newsletter is a real human who explicitly signed up to hear more from you, you might not want to keep them around if they haven't opened a single email from you in months. This is referred to as a number of different things across the industry ("list cleaning", "email scrubbing", "email hygiene"...) — we call it subscriber cleanup. It's an automatic opt-in process that checks for folks who are suspected to have abandoned their email address or have never engaged with your content. Removing these folks from your list might feel a bit like ripping off a band-aid (it can be sad to see the big subscriber count go down!) but is great for the long-term health of your subscriber base, because it means your engagement rate amongst your true fans will be higher.

(You can read more about subscriber clean-up here!)

A human eye

Last but not least, every single new Buttondown newsletter who imports subscribers from an external source goes through a manual approval process to make sure everything looks kosher. This is old-school, we know, but it's for the safety of you and every other author on the platform. We take our sending reputation and deliverability seriously, and this helps us maintain our best-in-class benchmarks on both fronts.

(If you're worried that this process is Kafka-esque and will take days on end, worry not — we generally complete it in less than eight hours during the week and less than 24 hours during the weekend.)

Offboarding people who don't pass our bar

A human eye is great, but it's not perfect, and circumstances can change — maybe an author starts abusing their API privileges or decides to otherwise violate Buttondown's terms of service by sending emails to folks who haven't signed up for them.

If you're found to have breached our internal threshold for either the number of emails you send that bounce or the number of emails you send that are marked as spam, we'll reach out to talk about your sending strategy. If those conversations don't go anywhere, you'll be removed from the platform.

(Sometimes, when we mention this, we're greeted with a bit of shock and dismay — "so you'll remove me just for sending more emails than usual?!" Buttondown's never off-boarded a well-meaning customer who made a mistake double-sending an email or accidentally imported bad subscribers; it's only ever been malicious actors.)

Pre-flight checks

Before sending your email, Buttondown runs a battery of 62 pre-flight verifications to make sure everything's in ship-shape. We check everything you can think of, like:

  1. Do you have specific words or phrases that Gmail or other inboxes will flag as spammy?
  2. Are any of your images too large?
  3. Did you use the word "attached" without actually attaching a file?
  4. Did you add too many images, meaning that some clients will refuse to load or send your email?

This validation suite makes sure you're sending out the best possible email, and the best possible email gets delivered at the best possible rate.

IP-based subscriber filtering

Buttondown works very hard to make sure all of the subscribers joining your newsletter are legitimate, so that they're not giving your publication a bad reputation. One of the first and most effective lines of defense is checking incoming subscriptions' IP addresses against a combination of both our internal datasets and those of trusted vendors like Spamhaus and Project Honeypot. (Note that we do this by pulling in omnibus data from external sources, rather than polling them, so as to protect the privacy of you and your subscribers.) This lets us immediately filter out automated or malicious bots subscribing to your newsletter.

No in-app cross-promo

One of the bigger product decisions Buttondown has made is to not push cross-promotion — this is the fancy industry term for "when someone subscribes to your newsletter, we suggest three similar newsletters for them to also subscribe to."

There are a number of reasons we do this — mostly, we don't think it's our place to get in between you and your audience — but the biggest one is it hurts everyone's deliverability. Studies that Buttondown's run show that subscribers who sign up for other newsletters through cross-promotion end up reporting emails as spam and unsubscribing at a much higher rate — even for the newsletter that they originally signed up for!

Other platforms tout growth through cross-promotion to juice your subscriber base; while you're of course free to run your own manual promotional efforts, it's not worth the risk to deliverability for us to push them on your behalf.

SPF and DKIM

You don't really need to know what these clumsy-sounding acronyms are, but they're protocols that we (along with many other reputable senders) use to ensure that the emails we send are coming from us, not someone pretending to be us.

Setting up SPF and DKIM are a bit of a hassle to handle yourself, but if you're sending from Buttondown it's automatically handled for you (even if you're sending from a custom domain!) And starting in 2024, Google requires all senders to send their emails with these authentication protocols in place.

We keep it easy for subscribers to unsubscribe

I'm sure this has happened to you:

  1. You bought something online.
  2. You started getting an email every. single. day. from the retailer.
  3. You finally got fed up and hit unsubscribe, except that page took you to another page which took you to another page.
  4. And then you still got an email the next day, because you unsubscribed from "weekly recommendations" but not "hot deals" or whatever.

Yeah — that drives us crazy too. Every email coming from Buttondown is one-click unsubscribe compliant, meaning that there's no labyrinthine set of hoops to jump through to unsubscribe. You might not love this as an author, but it's good for you in the long run — unhappy subscribers turn into frustrated subscribers, frustrated subscribers report your newsletter as spammy, and spam reports tank deliverability.

Emphasis on text over images

Buttondown's default email templates are very plain-text forward. This is nice for aesthetic reasons, but also is very positive on deliverability. Text-heavy, less rococo emails (as compared to their image-heavy counterparts) work great on inboxes of all sizes and shapes and score extremely well in content scanning, meaning that you'll be reaching more of your subscribers more reliably.

Bring your own domain

Last but not least, Buttondown lets you send from own domain (if you own one!) This improves the overall engagement rate for your emails, as they appear more personal and have a higher domain reputation. More importantly, that domain reputation carries with you — even if you leave Buttondown for another service, so long as that service also allows you to send from a custom domain.