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

推荐订阅源

让小产品的独立变现更简单 - 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 Subscribers can come from anywhere. Even another newsletter platform's form. Survey responses on the web How Brandon Lucas Green shares his music and supports artists Your newsletter's archives are more valuable than your list Better tag self-management Smarter automation filters Granular API keys Snippets New design settings pages Ask A Nerd: How does newsletter cadence affect deliverability? 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 Custom buttons now work in Markdown mode Ask a Nerd: Does attaching files to your newsletter hurt deliverability? Seline and Tinylytics support Unban subscribers Announcement bars for your archives Bang paths, source routing, and how email trips were planned Public postmortem: archive downtime 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 Reply to conversations Minimum viable complexity How Jeffery Hicks goes behind-the-scenes in his newsletter Changes to our stack in 2025 2026: Emails What the hell is a UTM? TK reminders in the editor Randomize survey answer order Why we insourced analytics Scroll sync in the editor 2026: Archives How Jamie Thingelstad uses Buttondown to explore tech topics How Kelly Jensen uses Buttondown to discuss key library issues 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
The legendary email client power users wouldn't let die
Ryan Farley · 2025-06-03 · via

Nearly 12 years after its end of life and 30 after its v1.0, fans of arguably the trendiest desktop email clients of all time came out of the woodwork, shouting Eudora’s praises. 

“Probably one of the few people left who still use it on a daily basis,” a Slashdot user wrote in response to the Computer History Museum releasing the email client’s source code. That hunch turned out to be pretty far afield.

“Eudora is a major reason my home desktop is still on OS X 10.6,” someone admitted in a Hacker News comment. “Eudora is on my machine to stay for the time being. It'll be there until the POP/IMAP protocol ceases to work!” another person proclaimed.

Then, there was the board chairman for the Computer History Museum himself. In the article announcing Eudora’s open-source status, Len Shustek insisted it was “the finest email client ever written, and it has yet to be surpassed. I still use it today.”

But if it was so great, why is Eudora buried in the archives instead of headlining a Wirecutter recommendation? There are many reasons. And somewhere further down that list is the one I find most interesting. 

Eudora was, from the very beginning, quirky software built for power users. Like a film director who respects their audience, skipping over exposition and letting them fill in the blanks. It’s not an approach that works for every app or newsletter or whatever else you’re creating. But when it works, people fight to keep your work alive.

First users in, last users out

A little more than a year after Steve Dorner began work on Eudora, writing an average of 4,000 lines of code per month, the University of Illinois released the email client for free in 1988. 

A few years later, Richard Stallman would publish the first General Public License and, paradoxically, Universities would shift from releasing their software in the public domain to thinking of it as a commercial asset. It was around that time when Qualcomm asked to buy (license, technically) Eudora and hire Dorner to continue developing it, a deal the University of Illinois was happy to take.

The first order of business after the change in management was to port the Mac-only version over to Windows for internal use among Qualcomm employees. They loved it. Project manager John Noerenberg recalls hearing "One financial executive at Qualcomm saying, 'I used to hate email. But I love Eudora!’”

Screenshot via University of Padua

A big part of what made Eudora so enjoyable to use was that it was one of the earliest email clients with a graphical user interface. That made it a breeze to experiment with and customize its unusually large featureset. You could, as early as version 1.4, schedule messages to send at specific times, edit your Quick Recipient list in the File menu, and switch between quoted-printable and base64 encoding to send messages with special characters at a time when English was the lingua franca of email.

Eudora became very popular very quickly. The team managing it grew alongside and invited users to send postcards about what they liked most in the software. Thousands of missives streamed in, disproportionately from people who lived and breathed email every day! It was participation bias and user-driven development at its best.

Software with personality

Qualcomm held off on monetizing Dorner’s software for a few years. But with 50 full-time employees working on it, that didn’t make sense for long. They rejigged Eudora into three tiers: Light (free), Sponsored (ad-supported) and Pro (paid). Even with the lowest tier, however, Eudora gave users far more flexibility and power than most other options of the time. 

Screenshot via Bertola.eu

Eudora Light 3.0 for Windows (which, fun fact, was coded in a completely different language, by a completely different team, than the Mac version) allowed multi-criteria custom filters, the ability to create emails from inside other software, and enough keyboard shortcuts to make power users weep. 

Later Mac versions included URI settings. You could copy a bit of code into a new message, and the string would automatically become a link. When clicked, URIs would let you change impossibly granular settings that weren’t listed anywhere in the software or its documentation. 

There was x-eudora-setting:32698, for instance, which let you set the maximum number of pixels in an image attachment for it to be downloaded automatically. Or setting 32662, to change the width of the function key labels in the toolbar. Or 7008, to edit the tooltip of the queue button. This sort of flexibility attracts the attention of particularly vocal users.

“[Eudora] has an incredible feature that every single mail client should have. Any feature in the menu list, any action there, can be added as a button,” Steve Wozniak gushed in a Lifehacker interview. “You can script actions to the buttons, too, so I can quickly copy messages to my assistants. There are scripts I wrote for joke lists so I can forward a message, remove the brackets and formatting, and make sure all the original attachments are included, to a pre-defined ‘joke’ group. Apple's Mail app just isn't scriptable enough to really handle my mail buttons.”

And the vibes. Eudora’s earliest notification pop-ups included a rooster with a letter in its beak when you had new mail and a snake when you didn’t. Because "The idea was that the rooster would have brought your mail, but the snake ate it first," Dorner told the New York Times.

Screenshot via Stanford University Helpdesk

Later, there would be a button for furling and unfurling message headers with BLAH, BLAH, BLAH written on it. Version 6 introduced MoodWatch, which labeled incoming and outgoing messages with chili peppers and ice cubes, depending on the presence of possibly offensive language. People loved it!

At its peak, Eudora served 18 million users and maintained a 63.5% worldwide market share among email clients. Unfortunately, the best-laid plans of devs and dotcoms often go awry. 

An onslaught of spam meant that email started to become more chore than delight. Users flocked to dumbed-down mailboxes and then-nascent social media. Those whose work took place in an inbox were having Outlook foisted on them. 

Qualcomm saw declining numbers and hit the eject button in 2006, discontinuing development. They wanted Eudora to be a blockbuster movie with characters who faced the camera and explained the plot, a forgettable product that generated millions. The people who sent those first postcards wanted something else.

Create for the crazy ones

It would be easy to view Eudora’s whipsaw growth and decline as a cautionary tale. In hindsight, Qualcomm almost certainly would have rather released Outlook than Eudora, would have preferred the software grow, and scale, and retain millions of users and billions of dollars. 

But not from Dorner’s perspective. His clout permitted him to say no to Qualcomm’s request that he relocate to California, instead working from home at a time when remote work was unheard of. He was allowed to develop Eudora the way he wanted, for the users he had in mind. "To have other people use and enjoy your program is probably what a certain breed of programmer is really interested in. That's the ultimate reward,” he said in his interview with the New York Times.

As of 2024, people were still putting hours into modernizing Eudora for current hardware. All because the guy who created it wanted to make something more quirky than boring, more challenging than facile–something that prioritized a small group of fervent fans above the rest.

Header screenshot via old.accesscom.com/support/macintosh/mac-eudora2.html