Self-host smtp4dev with Levelrail

Fake SMTP server that catches outgoing mail in a web inbox, for testing apps without sending real email.

  • Authorrnwood
  • LicenceBSD-3-Clause
  • Memory128 MiB
  • Services1

How to self-host smtp4dev

  1. Pull the images

    One image is pulled on your server.

    Show images
    • rnwood/smtp4dev:3.16.1
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on ports 80, 25.

  3. Fill in the secrets

    You do not have to fill in anything.

  4. 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 at port 25 of this container and open the address to read what it sent. It has no login, so keep it private.

smtp4dev requirements

Memory
About 128 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
80, 25
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
BSD-3-Clause, 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 smtp4dev. 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 smtp4dev docs page.

Deploy smtp4dev your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy smtp4dev from the CLI

levelrail-cli templates deploy smtp4dev --name my-smtp4dev

Deploy smtp4dev with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/smtp4dev/deploy

smtp4dev configuration

smtp4dev services

ServiceImagePortsVolumes
smtp4dev rnwood/smtp4dev:3.16.1 80, 25 data -> /smtp4dev

smtp4dev environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
80, 25
Volumes
1 named mount: data -> /smtp4dev

smtp4dev FAQ

How much memory does smtp4dev need?

The catalog lists about 128 MiB of memory for smtp4dev.

Does smtp4dev run on arm64?

For smtp4dev, arm64 support is not confirmed; amd64 is unknown.

What licence is smtp4dev under?

smtp4dev is licensed under BSD-3-Clause, which is permissive, with few conditions on reuse.

Does smtp4dev need configuration before it starts?

No. The template fills in its own defaults.

Which ports does smtp4dev use?

smtp4dev listens on ports 80 and 25 inside the stack.

Where does smtp4dev keep its data?

In a named volume: data mounted at /smtp4dev.

Can I deploy smtp4dev 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 smtp4dev, 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 rnwood/smtp4dev:3.16.1 is what you deploy there.

levelrail-cli templates deploy smtp4dev --name my-smtp4dev