A few weeks ago, I shared WhelkMail here. It started as a personal project after Google's announcement about discontinuing Gmail's support for checking external email accounts through POP3, and eventually grew into something I wanted to make available to others.
Since the initial release, I've been spending quite a bit of time improving it. Rather than just adding features, much of the work has focused on making it more reliable and practical for everyday use.
There's now also a demo available!
If you'd like to see what WhelkMail looks and feels like before installing your own instance, you can try the demo here:
Try the WhelkMail demo
It comes with a preconfigured mailbox and sample emails, so you can explore the interface without having to connect your own email accounts.
What's changed since the initial release?
1. IMAP synchronization
This has probably been the biggest area of development. I've been working on incremental synchronization, resumable operations, database locking and better handling of multiple accounts. Getting IMAP synchronization right is considerably more complicated than I initially expected.
2. Performance
I've been addressing some of the performance issues that became apparent when using larger mailboxes, particularly Gmail accounts. This includes improvements to message loading, database queries, caching and background synchronization.
3. Email management
I've continued improving the everyday email workflow, including message handling, drafts, folders, labels, filters and bulk operations. The goal is to make managing multiple accounts feel as seamless as using a single mailbox.
4. Sending and account compatibility
I've also been working on email delivery, SMTP compatibility and the interaction between outgoing messages and IMAP folders. Supporting different providers consistently is one of those things that sounds simple until you start dealing with their individual quirks.
WhelkMail also now has experimental compatibility with Cloudflare Email Service, opening up some interesting possibilities for people already using Cloudflare for their domains and email routing. This integration is still experimental and shouldn't be considered production-ready.
5. Easier installation
I've also started working on a dedicated installer to make deploying WhelkMail easier, especially for people who aren't comfortable working with command-line tools.
The installer is currently in beta, so there's still work to do, but the goal is to make setting up a self-hosted instance much less intimidating.
6. Security and reliability
I've continued reviewing the security boundaries, credential handling and server-side operations. For something that handles people's email accounts, these aspects deserve considerably more attention than just getting the interface working.
What's next?
There are still plenty of things I'd like to improve.
I'm particularly interested in further simplifying deployment, improving the mobile experience and exploring better notification options. The PWA approach works, but browser-based notifications still have limitations compared with native mobile applications.
A few things worth remembering
WhelkMail is still an actively developed project, not a finished commercial product.
It's a self-hosted webmail client, not an email hosting service. You bring your existing IMAP/SMTP accounts, and WhelkMail provides a unified interface for managing them.
It runs on Cloudflare (Pages Functions, D1 and Cloudflare's TCP socket support), without requiring a VPS or a traditional mail server.
It's open source and MIT licensed.
Links
If you haven't seen the project before, the README and documentation are a good place to start.
I'd be interested in hearing from anyone who tries it, especially if you're using multiple email providers or have particularly large mailboxes.
Bug reports, suggestions and constructive criticism are always welcome!