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

推荐订阅源

J
Java Code Geeks
F
Fortinet All Blogs
Martin Fowler
Martin Fowler
M
MIT News - Artificial intelligence
G
Google Developers Blog
P
Proofpoint News Feed
Recent Announcements
Recent Announcements
MyScale Blog
MyScale Blog
D
DataBreaches.Net
Stack Overflow Blog
Stack Overflow Blog
月光博客
月光博客
爱范儿
爱范儿
罗磊的独立博客
腾讯CDC
Hugging Face - Blog
Hugging Face - Blog
博客园 - 叶小钗
Vercel News
Vercel News
酷 壳 – CoolShell
酷 壳 – CoolShell
B
Blog
C
Check Point Blog
美团技术团队
宝玉的分享
宝玉的分享
Microsoft Security Blog
Microsoft Security Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻

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
Cleaner subscriber management
Justin Duke · 2025-07-28 · via Buttondown's blog

Hey folks! We've made some behind-the-scenes improvements to how we handle problematic subscribers that should make your life a bit easier.

A brief history lesson

When Buttondown first launched, we used a single flag, is_spammy, to mark subscribers who were problematic—whether their email was missing, malformed, or looked like it came from a bot. Over time, we added more specific types, like "malformed," to better describe these cases. Eventually, this led to a long list of subscriber types that all meant, in practice, "we can't deliver to this address."

However, this approach had two main issues. First, the term "spammy" suggested intentional bad behavior, which often was not true. Second, the actions you could take on these subscribers were basically the same, regardless of the specific type. So, having lots of categories just added confusion without real benefit.

To simplify things, we've now consolidated several of these types—like "malformed" and "spammy"—into a single "undeliverable" status. All subscribers we can't deliver to are now grouped together, but with a specific reason attached (e.g., malformed address, flagged by our systems, etc.). This makes it easier to see why someone can't receive emails, filter your list, and automate actions.

There are still a few other "bad" subscriber types: "complained," "disposable," and "blocked." But for most cases, you'll just see "undeliverable" with a clear reason.

In short: instead of juggling multiple confusing categories, you now have a single, clearer "undeliverable" status for subscribers we can't reach, making management and automation much simpler.

What do you need to do?

Nothing! This change happened automatically. If you had any subscribers marked as "spammy," they're now marked as "undeliverable" with the appropriate reason. Your existing filters and segments will continue to work as expected.

This is part of our ongoing effort to make subscriber management more intuitive while giving you the detailed information you need to maintain a healthy list.