SnappyMail vs Roundcube

The source material uses RainLoop. RainLoop is abandoned and its community fork, SnappyMail, is the current equivalent. The other main option for self-hosted webmail is Roundcube. The two take different approaches and understanding the difference is worth a brief note before committing to either.

RainLoop / SnappyMail

RainLoop was written to be fast and minimal. SnappyMail, its maintained fork, renders email significantly faster than Roundcube, uses less RAM, and has a cleaner default UI. PGP encryption is built in with no plugins needed.

The architecture reflects its priorities: no database required by default, configuration stored in flat files, quick to install and quick to load. It is a webmail client in the narrow sense: read, write, manage folders.

The trade-offs are real. The plugin ecosystem is smaller than Roundcube’s. SnappyMail is the most active of the current webmail options in terms of code commits, but its community is considerably smaller than Roundcube’s. Some features that Roundcube exposes through a polished GUI require raw Sieve scripting in SnappyMail.

Roundcube

Roundcube is the most mature self-hosted webmail client, used by thousands of hosting providers worldwide. The three-pane layout is immediately familiar to anyone who has used Outlook or Thunderbird. Plugins extend functionality with everything from two-factor authentication to CardDAV address books.

Roundcube is 58 times more popular than SnappyMail by deployment count. The community is large, the documentation is extensive, and the plugin ecosystem covers almost any requirement. If something needs doing in webmail, there is almost certainly a Roundcube plugin for it.

The trade-offs are also real. Roundcube is heavier than SnappyMail, requires a database, and has a more complex installation. The interface is functional but dated compared to SnappyMail’s cleaner aesthetic.

The decision for this series

SnappyMail is the choice here for three reasons.

First, this series uses Evolution as the primary mail client on the desktop. Webmail is a fallback, not a primary interface. The lightweight approach of SnappyMail is appropriate for that role.

Second, SnappyMail’s no-database default simplifies the deployment. One less service to configure and maintain for a component that is not central to the setup.

Third, the performance advantage matters for occasional use from mobile or an unfamiliar machine. A fast-loading interface is more pleasant when you are not on your usual hardware.

If webmail were the primary mail interface for multiple users, Roundcube would be the stronger choice: more features, more polished filter management, and a larger support community. For this setup, SnappyMail is the right fit.