Self-host MailDev with Levelrail
A local SMTP server that catches outgoing mail and shows it in a web inbox, for testing mail from your apps. Mail sent to maildev:1025 from other services in this project appears in the web page and is never delivered.
- Authormaildev
- LicenceMIT
- Memory128 MiB
- Services1
How to self-host MailDev
-
Pull the images
One image is pulled on your server.
Show images
maildev/maildev:2.2.1
-
Create the app
One service starts in a single Compose app, on ports 1080, 1025.
-
Fill in the secrets
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
- Point your app SMTP host at maildev, port 1025, with no login, then open the page to read caught mail.
MailDev requirements
- Memory
- About 128 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 1080, 1025
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive 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 MailDev. 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 MailDev docs page.
Deploy MailDev your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy MailDev from the CLI
levelrail-cli templates deploy maildev --name my-maildev Deploy MailDev with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/maildev/deploy MailDev configuration
MailDev services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| maildev | maildev/maildev:2.2.1 | 1080, 1025 | none |
MailDev environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 1080, 1025
- Volumes
- none
MailDev FAQ
How much memory does MailDev need?
The catalog lists about 128 MiB of memory for MailDev.
Does MailDev run on arm64?
For MailDev, arm64 support is not confirmed; amd64 is unknown.
What licence is MailDev under?
MailDev is licensed under MIT, which is permissive, with few conditions on reuse.
Does MailDev need configuration before it starts?
No. The template fills in its own defaults.
Which ports does MailDev use?
MailDev listens on ports 1080 and 1025 inside the stack.
Can I deploy MailDev 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 MailDev, 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 maildev/maildev:2.2.1 is what you deploy there.