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

推荐订阅源

SecWiki News
SecWiki News
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
V
Visual Studio Blog
博客园 - 叶小钗
S
SegmentFault 最新的问题
IT之家
IT之家
大猫的无限游戏
大猫的无限游戏
博客园_首页
Apple Machine Learning Research
Apple Machine Learning Research
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
月光博客
月光博客
酷 壳 – CoolShell
酷 壳 – CoolShell
腾讯CDC
D
Darknet – Hacking Tools, Hacker News & Cyber Security
V
V2EX
阮一峰的网络日志
阮一峰的网络日志
L
Lohrmann on Cybersecurity
量子位
C
Cyber Attacks, Cyber Crime and Cyber Security
T
Tor Project blog
J
Java Code Geeks
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
博客园 - 三生石上(FineUI控件)
Attack and Defense Labs
Attack and Defense Labs
AI
AI
The Cloudflare Blog
T
Tailwind CSS Blog
S
Schneier on Security
爱范儿
爱范儿
PCI Perspectives
PCI Perspectives
Stack Overflow Blog
Stack Overflow Blog
S
Secure Thoughts
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
T
The Exploit Database - CXSecurity.com
博客园 - 【当耐特】
V2EX - 技术
V2EX - 技术
S
Securelist
P
Proofpoint News Feed
T
Threat Research - Cisco Blogs
Help Net Security
Help Net Security
C
Cisco Blogs
N
News and Events Feed by Topic
人人都是产品经理
人人都是产品经理
B
Blog RSS Feed
K
Kaspersky official blog
T
The Blog of Author Tim Ferriss
G
Google Developers Blog
S
Security Affairs
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
Simon Willison's Weblog
Simon Willison's Weblog

Buttondown's blog

Email could have been X.400 times better The physicists who convinced Fermilab to send Brazil's emails Better in-app previews Analytics 3.0 Subscriber ID variables Comments! Send latest premium action Automation filtering Free API subscribers Surveys in automations Reply to replies Labels for RSS feeds How Jeremy Singer-Vine curates curious datasets for readers 2023 (and what's next) Email vs web content Sort by engagement Better gift subscriptions How Andy Dehnart built a career reviewing television New email template Email-based automations Opt-in reply tracking Automatic alt text More social network integrations Sort by metadata Overlarge image warnings Automation tag actions Pause emails mid-flight Search tags and automations Gift via automations Subscriber-driving emails Programmatic webhooks Email page views Tag statistics Discord webhook formatting Automatic subscriber cleanup RSS subscriber count Weekly subscriber reports More list columns Customizable list views How Max Voltar turned a side gig into a trusted keyboard resource How Nick Disabato runs two newsletters from one design consultancy Made-for-you share images Automation improvements End-of-email surveys Filter by date Survey-triggered automations More automation functionality New webhooks How France Insider built a news service with paid subscribers Email as primary key How John Willshire unites two businesses in one newsletter Confirmation reminders Email churned subscribers Email-to-draft Subscriber metadata columns ChatGPT integration Faster web archives Referral program Better search results TikTok embeds Subscriber timeline Spotify embeds Improved RSS-to-email Subscribe page OG image New analytics page Google Tag Manager Even more subscriber types Integrating Duda with Buttondown Linktree integration guide Advanced and enterprise plans Framer integration guide API requests page Team collaboration In-email surveys Better CSS settings Better RSS automation fetching! Editor toolbar improvements Smart filters Faster emails page RSS automations Faster email analytics Zapier error codes Image accessibility checks Tags vs newsletters OG image picker Image editor improvements API bulk actions Improved OpenAPI spec Mastodon support Better subscriber filtering Better subscriber validation Hotkey support! Programmatic access to analytics Stronger bulk actions Faster archive page Custom canonical URLs Email slug and metadata Improved writing interface Generating a Typescript router in Django Filter emails by source
How we keep deliverability high
Justin Duke · 2023-11-02 · via Buttondown's blog

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.