Mozilla keeps Eudora alive, releases new version based on Thunderbird
The Eudora team might have called it quits on commercial aspirations and released the product as open source some time ago, but that doesn't mean you should get the trash bin out just yet.
Context & Ripple Effects
The Eudora story here is a controlled landing rather than a shutdown: the team had already given up on selling the client and released the code as open source, and Mozilla's response is to keep the name alive by rebuilding the product on its own Thunderbird codebase. One codebase now carries two brands, with Mozilla absorbing maintenance duty for a veteran mail client whose original owners walked away.
It also lands during a crowded stretch for Mozilla — the same summer saw the first Firefox 3 beta pushed back twice over performance regressions, an unpatched firefoxurl URI-handler vulnerability left open, and SQLite-backed offline storage confirmed for Firefox 3's Places feature. Committing engineering to a Thunderbird-based Eudora signals Mozilla treats mail as a second pillar alongside a browser under visible strain.
First-order effects
- Existing Eudora users get a maintained upgrade path on Thunderbird's engine instead of an orphaned commercial product, while Mozilla gains a second branded desktop client at near-zero incremental codebase cost.
- Thunderbird becomes the shared substrate for two mail brands, so bugs, security fixes, and feature work land once and serve both lineages — raising the stakes on every Thunderbird release decision.
Second-order effects
- Desktop mail rivals such as Microsoft's Outlook now compete against an open-source stack that Mozilla can field at zero license cost, pressuring the paid-client tier of the market.
- Extension developers and enterprise mail administrators gain one ecosystem to target instead of two, concentrating add-on and migration tooling investment around Thunderbird-derived clients.
Third-order effects
- If the pattern holds, aging commercial desktop applications increasingly survive as branded skins over community-maintained open cores, with value migrating from license sales to support and integration.
- Mozilla's structure drifts toward that of a multi-client platform steward — browser and mail both — which raises governance questions about how far a foundation funded largely by browser search deals can subsidize adjacent clients.
The trend: Legacy commercial desktop software is being kept alive by re-basing it on open-source cores stewarded by foundations, trading ownership of the code for continuity of the brand.