Set up listmonk on this VM by following the exe.dev recipe at https://exe.dev/deploy/listmonk.md?via=terminal from top to bottom. The recipe's example VM name is my-listmonk. This VM's name is the output of `hostname`: use it wherever the recipe writes my-listmonk. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - listmonk 6.2 on PostgreSQL 17, restarted after a reboot. - A private admin on port 9000 and a public port that answers only subscriber-facing paths. - Links in emails that point at https://.exe.xyz, not localhost. - A test inbox that catches all mail until the owner connects SES, Postmark or Resend. - Nightly backups of the database, uploads and secrets. Read the whole recipe, including closed details, and follow "Install by hand" first. The walkthrough before it is for the owner afterwards. Do not run the Restore or Update instructions. Work as exedev in ~/listmonk. Never overwrite an existing ~/listmonk/.env. Do not connect an email provider, import subscribers or send campaigns: the owner does that. Leave public sharing off; only the owner can turn it on. Verify docker.service is enabled, the four containers are restart unless-stopped and up (db and app healthy), localhost:9000/health answers {"data":true}, localhost:8000/subscription/form returns 200, and localhost:8000/admin/ and localhost:8000/api/lists return 404. Check the backup timer is enabled and the first dump exists in ~/listmonk/backups. Finish with the admin URL on port 9000, the user name admin and the password from LISTMONK_ADMIN_PASSWORD in ~/listmonk/.env, the test inbox URL on port 8025, and the command the owner runs on their own computer to make subscriber pages public: ssh exe.dev share set-public my-listmonk Finish with the URLs I should open and these commands, which only I can run, from my own computer (with this VM's name in them): ssh exe.dev share set-public my-listmonk # subscribers' unsubscribe and opt-in links need this