English
SnappyMail Hosting
Read and send email from any IMAP mailbox through a fast, modern webmail client.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Official links
SnappyMail’s official links and original website
SnappyMail Website
More
Tech
- Docker image
- djmaze/snappymail:latest
- Default port
- 8888
How SnappyMail works
SnappyMail is a webmail client. A user signs in with credentials for an existing mail domain, reads and organises messages over IMAP, and submits outgoing mail through that provider’s SMTP service. The interface can handle folders, search, identities, contacts, message composition, attachments, and optional Sieve filtering where the connected server supports it.
The application does not store or deliver the underlying mailbox by itself. Its administrator panel is used to define domains, IMAP and SMTP endpoints, security settings, plugins, and other client behaviour. The catalogue persists /var/lib/snappymail; the generated administrator password is written inside _data_/_default_/admin_password.txt and should be changed after the initial sign-in.
Key SnappyMail features
SnappyMail is designed without a relational database requirement and uses file-based application data. Mail content generally remains on the connected IMAP server, while client settings, caches, contacts, and configuration may live in the application storage. Administrators must understand both sides when planning recovery: restoring the web client does not restore a mailbox held by another provider.
the hosting service does not provide an email account, IMAP server, SMTP service, domain mail records, spam filtering, sender reputation, or mailbox support through this package. The standing application-email restriction also means SnappyMail should not be described as a platform mail service. Each user must connect an authorised provider, and that provider controls quotas, retention, authentication, and deliverability.
Who uses SnappyMail
People can reach a private-domain mailbox from a browser, small organisations can give staff a consistent web client for an existing mail server, and administrators can offer web access when the provider’s own interface is unsuitable. Multiple domains can be configured when their connection details and policies are understood.
SnappyMail is not a mailbox host, migration service, email archive, marketing platform, compliance gateway, or replacement for provider-side security. Operators remain responsible for protecting the administrator panel, choosing TLS settings, managing plugins, respecting mailbox policies, and responding to compromised user or provider credentials.
Self-hosting SnappyMail: requirements and cost
SnappyMail resource use is driven by concurrent web sessions, large folders, searches, attachments, contacts, plugins, cache activity, and latency to the connected IMAP and SMTP servers. PostgreSQL and MariaDB are Not required; persistent client configuration lives under /var/lib/snappymail. The software has no separate application charge, while mailbox storage and message delivery remain with the external email provider.
On AvaHost, SnappyMail uses Plan 1 at €2. The hosted SnappyMail package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. Retrieve and replace the generated administrator password, then configure only mail domains and endpoints you are authorised to use. The hosted package does not include mailboxes, IMAP or SMTP service, DNS mail records, provider support, deliverability, spam handling, or application email. Back up both the SnappyMail configuration and the actual mailbox through its provider.
F.A.Q
SnappyMail starts at €2 on Plan 1. That starting point suits light webmail use against an existing provider. Concurrent users, very large folders, searches, attachment handling, contacts, plugins, cache size, and the response time of the connected IMAP and SMTP servers determine whether additional capacity is useful.
The hosted package supplies the SnappyMail web client only. You need an existing compatible mailbox and the authorised IMAP and SMTP settings from its provider. AvaHost does not create the email account, supply outbound delivery, configure domain mail records, manage spam filtering, or restore messages held by the external server.
The container writes the generated administrator password to `_data_/_default_/admin_password.txt` inside the persistent application storage. Sign in at the administrator path, replace that password, and restrict access before adding real domains. Keep a protected recovery record because application email is not available for account recovery.
A custom domain can point to SnappyMail, with automated HTTPS applied after DNS is configured. Test the administrator panel, user sign-in, IMAP folders, SMTP submission, attachments, and logout on the final hostname. Browser HTTPS does not replace secure connections and certificate validation to each configured mail provider.