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.

  1. 01recondistro (apt or dnf) and EL version
  2. 02reconRspamd already present? active?
  3. 03reconexisting local overrides (redis.conf, worker-controller.inc) to preserve
  4. 04reconRedis/Valkey present and active (expected backend)?
  5. 05reconRspamd ports 11332-11334 free?
  6. 06reconPostfix present? milters already configured (e.g. OpenDKIM) to keep
  7. 07actAdd the official Rspamd repositoryverify
  8. 08actInstall Rspamd + Redisverify
  9. 09actConnect Redis (only if missing)verify
  10. 10actController password (only if missing)verify
  11. 11actEnable and startverify
  12. 12actWire into Postfix (only if Postfix is installed)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.

  1. 01Add the official Rspamd repositoryVerified byapt-cache policy rspamd 2>/dev/null | grep -c rspamd.com || dnf info rspamd -q | grep -c Version
  2. 02Install Rspamd + RedisVerified byrspamd --version
  3. 03Connect Redis (only if missing)Verified byrspamadm configtest
  4. 04Controller password (only if missing)Verified bygrep -c "^password" /etc/rspamd/local.d/worker-controller.inc && rspamadm configtest
  5. 05Enable and startVerified bycurl -s http://127.0.0.1:11334/ping
  6. 06Wire into Postfix (only if Postfix is installed)Verified bypostconf -h smtpd_milters

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

Never edit files in /etc/rspamd outside local.d/ and override.d/. The controller (11334) stays on 127.0.0.1, never exposed publicly. milter_default_action = accept: an Rspamd outage must not block mail. Do not replace existing milters.

SEC.04

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.

recipe — fail2ban_setup150+ in catalogue
security4 steps · low risk · idempotentrun
reconsshd present? ufw active? existing jails?✓
actinstall fail2ban · write default jails✓
actenable service · restart sshd (safe)✓
verifytest ban 60s · jails active · sshd alive✓

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.05

Deploy on Servor button

Maintain Rspamd 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.

Deploy on ServorDark background
Deploy on ServorLight background
[![Deploy on Servor](https://servor.app/badges/deploy-on-servor.svg)](https://servor.app/deploy/install-rspamd)

SEC.06

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.