Install maddy and configure domain identity and TLS

maddy models the mail path as configured modules. Its setup tutorial covers host identity, domains, certificates, and service setup; match examples to the release you install rather than copying a historical image tag.

For the choice between an integrated server and separate daemons, see maddy in our Linux mail-server comparison.

Prepare the service

1. Select a supported package, release build, or container and follow its service-user/storage instructions.
2. Configure the actual hostname, primary_domain, and local_domains values in the deployed configuration.
3. Set DNS and PTR for the real mail host, checking both advertised address families.
4. Configure the certificate/key paths with access for the unprivileged maddy service identity.

maddy’s tutorial emphasizes that it does not run as root, even at startup. Fix certificate permissions narrowly; do not make a private key publicly readable. Review its supported automatic certificate-management or renewal/reload behavior.

Verify before account migration

Confirm service startup, listener bindings, trusted TLS, and a controlled recipient’s configured delivery path. Test unknown-recipient and unauthorized-relay rejection before moving MX.

The project explicitly labels its IMAP storage beta on the official site. Decide whether that is suitable for your mailbox requirements or whether to use a separate mature store. SMTP readiness does not establish mailbox durability or compatibility with every client feature.