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.
- 01recondistro (apt or dnf) and EL version
- 02reconDovecot already present? version 2.3 or 2.4 (different syntax)? active?
- 03reconexisting config (ssl, auth, mail_location) to preserve
- 04reconIMAP/POP3 ports already taken?
- 05reconLet’s Encrypt certificates available? MTA present for delivery?
- 06reconfirewall active (ufw or firewalld)?
- 07actInstall Dovecot IMAPverify
- 08actRequire TLS, refuse cleartext authverify
- 09actEnable and restartverify
- 10actCertificate served (only if a domain is provided)verify
- 11actOpen IMAPS 993 (only if a firewall is active)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 Dovecot IMAPVerified by
dovecot --version - 02verifyRequire TLS, refuse cleartext authVerified by
doveconf -n | grep -E '^ssl = required' - 03verifyEnable and restartVerified by
systemctl is-active dovecot && ss -tlnH "sport = :993" | grep -c LISTEN - 04verifyCertificate served (only if a domain is provided)Verified by
openssl s_client -connect 127.0.0.1:993 -servername ${domain} </dev/null 2>/dev/null | openssl x509 -noout -subject | grep -c ${domain} - 05verifyOpen IMAPS 993 (only if a firewall is active)Verified by
ufw status 2>/dev/null | grep -c 993 || firewall-cmd --list-services | grep -c imaps
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Never allow cleartext auth without TLS. Do not edit the stock files in /etc/dovecot: override in conf.d/99-servor.conf. Do not change mail_location on an existing install (risk of losing mailbox access). Only open 993.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${domain} | Let’s Encrypt certificate 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 Dovecot IMAP 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.
- 02RspamdRspamd anti-spam filter + Redis (official repo), wired into Postfix if present.
- 03ListmonkListmonk newsletter management + Postgres via Docker Compose, admin with a random password.
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.