SEC.01
The playbook
The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.
- 01reconDocker Engine + compose plugin present and daemon active?
- 02reconListmonk already deployed? existing data volume?
- 03reconexisting compose.yaml or .env in /opt/listmonk? do not overwrite
- 04reconport 9000 free? otherwise who holds it
- 05reconreverse proxy present (only useful if a domain is provided)
- 06actInstall Docker Engine (only if missing)verify
- 07actGenerate the secretsverify
- 08actWrite the compose fileverify
- 09actStartverify
- 10actTLS reverse proxy (only if a domain is provided)verify
SEC.02
What it verifies
Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.
- 01verifyInstall Docker Engine (only if missing)Verified by
docker compose version && systemctl is-active docker - 02verifyGenerate the secretsVerified by
stat -c '%a' /opt/listmonk/.env && grep -c LISTMONK_ADMIN_PASSWORD /opt/listmonk/.env - 03verifyWrite the compose fileVerified by
docker compose -f /opt/listmonk/compose.yaml config -q && echo ok - 04verifyStartVerified by
curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:9000/admin/login - 05verifyTLS reverse proxy (only if a domain is provided)Verified by
curl -s -o /dev/null -w '%{http_code}' https://${domain}/admin/login
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Never overwrite an existing /opt/listmonk/.env or compose.yaml, never delete the listmonk-data volume. Admin credentials are in /opt/listmonk/.env. Postgres is not exposed, the app listens on 127.0.0.1. Remind to configure a valid SMTP in Settings before any send.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${domain} | Domain (optional) |
SEC.05
How a recipe runs in Servor
Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.06
Deploy on Servor button
Maintain Listmonk or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.
SEC.07
More mail recipes
- 01SMTP relay (Postfix)Postfix as an outbound relay (satellite) via an authenticated TLS smarthost. Destructive: reconfigures mail delivery.
- 02Dovecot IMAPDovecot IMAP server, TLS required, IMAPS on :993.
- 03RspamdRspamd anti-spam filter + Redis (official repo), wired into Postfix if present.
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.