NextSnapMail is an independent community fork of SnappyMail, focused exclusively on providing and maintaining the webmail client as an app for Nextcloud.
The project continues development of the existing SnappyMail codebase for the Nextcloud use case. It is not an official continuation of SnappyMail and is not affiliated with, endorsed by, or sponsored by Nextcloud GmbH.
Warning
NextSnapMail is under active development and is not yet ready for production use. Anyone installing, testing, or using it does so at their own risk. There is no warranty, and users are responsible for backups and for protecting their own systems, accounts, credentials, and data.
The following foundation and compatibility work has been completed on the
master branch:
- established the NextSnapMail project identity, scope, provenance, license, and trademark documentation (#1);
- restored operation with Nextcloud 34 by replacing removed server APIs, updating Content Security Policy integration, and bundling the required Nextcloud plugin with app builds (#2);
- added automatic PHP syntax checks for PHP 8.2, 8.3, 8.4, and 8.5 (#2);
- repaired saving messages and attachments to Nextcloud Files and attaching files from Nextcloud, including verified file sizes, MIME types, modification times, ETags, and duplicate filename handling (#3);
- preserved credentials stored in personal settings during temporary network, DNS, TLS, or mail-server outages (#4);
- separated the Nextcloud app identity as
nextsnapmail, set the initial NextSnapMail app version to0.1.0, added dedicated NextSnapMail settings sections, bundled available extensions with the app package, removed the dependency on the former SnappyMail package service for extension and core update checks, and sorted active extensions first in the admin extension list (#6); - published signed Nextcloud app releases through the Nextcloud App Store and
fixed release package integrity issues caused by forbidden
.htaccessfiles in App Store installations; - fixed S/MIME signing with unencrypted private keys in the packaged Nextcloud app while preserving UTF-8 encoded folder emojis and other special characters in the JavaScript assets.
The Nextcloud 34 compatibility, file transfer, and credential-preservation changes have also been tested manually on running Nextcloud installations.
Important work still in progress includes removing the temporary
unsafe-eval Content Security Policy allowance, improving the reproducible
Nextcloud-only release process, documenting the migration path for existing
SnappyMail installations, and continuing signed Nextcloud app releases.
NextSnapMail is currently in the initial restructuring phase.
The repository still contains the inherited SnappyMail webmail core and several
legacy integration and release files. The Nextcloud app identity has been
separated as nextsnapmail and will be reviewed and migrated incrementally.
Please test NextSnapMail carefully before using it in production.
NextSnapMail intends to maintain:
- the SnappyMail webmail core required by the Nextcloud app;
- integration with current supported Nextcloud releases;
- IMAP, SMTP, Sieve, contacts, calendar, and file integration used through Nextcloud;
- a self-contained Nextcloud app package and release process;
- security, compatibility, accessibility, and localization fixes.
The project does not intend to publish or maintain separate distributions for:
- Docker or standalone container images;
- ownCloud;
- Cloudron, cPanel, CyberPanel, HestiaCP, Virtualmin, or similar hosting panels;
- Debian, Arch Linux, or other system packages;
- standalone SnappyMail installations outside Nextcloud.
This scope describes the direction of the project. Files for unsupported targets remain in the repository during the initial migration and will only be removed after their dependencies have been reviewed.
- Establish the NextSnapMail project identity and preserve provenance.
- Stabilize the new Nextcloud app identifier and document the migration path.
- Bundle the required Nextcloud integration without relying on the former SnappyMail package service.
- Introduce a reproducible Nextcloud-only build and test process.
- Modernize the integration for supported Nextcloud and PHP versions.
- Publish signed, source-backed Nextcloud app releases.
The contribution workflow and compatibility targets are still being prepared. Bug reports and changes should be submitted to the NextSnapMail repository.
Please avoid large mechanical renames of the internal RainLoop and
SnappyMail namespaces. They are part of the inherited architecture and will
be migrated only where doing so is technically justified.
NextSnapMail is based on SnappyMail, which is itself a fork of RainLoop Webmail Community Edition.
The NextSnapMail project began modifying and restructuring the codebase on 2026-06-18. A summary of inherited projects and contributors is maintained in CREDITS.md. Project changes are recorded in Git history and will be documented in release notes.
Copyright notices from SnappyMail, RainLoop, and bundled third-party components must remain intact:
- Copyright (c) 2020 - 2024 SnappyMail
- Copyright (c) 2013 - 2022 RainLoop
- Copyright for NextSnapMail modifications belongs to their respective contributors
This project remains licensed under the GNU Affero General Public License, version 3 (AGPLv3). See LICENSE for the complete terms.
Modified versions must retain applicable notices, identify modifications, and remain available under the AGPL. Users interacting with a modified version over a network must be offered access to its corresponding source code as required by section 13 of the AGPLv3.
Bundled third-party components may carry additional compatible license and copyright notices. Those notices remain applicable to their respective files.
NextSnapMail is an independent project. "Nextcloud" and the Nextcloud logo are trademarks of Nextcloud GmbH. The Nextcloud name is used only to describe compatibility and the intended platform. See TRADEMARKS.md.