Self-host SnappyMail with Levelrail
A fast, light webmail client that connects to your IMAP and SMTP servers.
- Authorthe-djmaze
- LicenceAGPL-3.0-only
- Memory128 MiB
- Services1
How to self-host SnappyMail
-
Pull the images
One image is pulled on your server.
Show images
djmaze/snappymail:v3.0.1.1
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8888.
-
Fill in the secrets
1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- The admin panel is at /?admin and its generated password is in the data volume under _data_/_default_/admin_password.txt.
SnappyMail requirements
- Memory
- About 128 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 8888
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0-only, network copyleft (agpl) license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then SnappyMail. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the SnappyMail docs page.
Deploy SnappyMail your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy SnappyMail from the CLI
levelrail-cli templates install snappymail --name my-snappymail Deploy SnappyMail with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/snappymail/install \
-d '{
"name": "my-snappymail"
}' SnappyMail configuration
SnappyMail services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| snappymail | djmaze/snappymail:v3.0.1.1 | 8888 | data -> /snappymail/data |
SnappyMail environment variables
| Variable | Service | Value |
|---|---|---|
| TZ | snappymail | Preset by the template |
Ports and volumes
- Ports
- 8888
- Volumes
- 1 named mount: data -> /snappymail/data
SnappyMail FAQ
How much memory does SnappyMail need?
The catalog lists about 128 MiB of memory for SnappyMail.
Does SnappyMail run on arm64?
For SnappyMail, arm64 support is not confirmed; amd64 is unknown.
What licence is SnappyMail under?
SnappyMail is licensed under AGPL-3.0-only, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does SnappyMail need configuration before it starts?
No. The template fills in its own defaults.
Which ports does SnappyMail use?
SnappyMail listens on port 8888 inside the stack.
Where does SnappyMail keep its data?
In a named volume: data mounted at /snappymail/data.
Can I deploy SnappyMail on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for SnappyMail, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image djmaze/snappymail:v3.0.1.1 is what you deploy there.