Generate a mox deployment with quickstart

mox’s quickstart generates a coherent configuration for a small mail deployment. Start on a dedicated host with permitted mail ports and a real hostname, not a production machine whose existing web/mail listeners will be overwritten.

If you are still choosing an integrated server, see mox in our Linux mail-server comparison.

Generate and inspect the setup

1. Obtain a trusted release/build through the installation guide and create the documented service user/directories.
2. Run the release’s quickstart for an address on your controlled test domain. This creates configuration and credentials; review output privately.
3. Inspect generated mox.conf, domains.conf, DNS instructions, and the proposed service setup before starting it.
4. Publish only the approved DNS changes and protect administrative access and generated passwords.

mox documents that its automatic ACME/web setup expects suitable HTTP/HTTPS access; combining it with another webserver requires the explicit supported configuration, not a blind port change.

Verify the generated configuration

Use the command reference for read/check operations such as configuration testing and domain DNS checks. They diagnose readiness, not guaranteed inbox placement.

Test a controlled mailbox and SMTP path before moving production MX. Confirm PTR/hostname alignment, IPv4/IPv6 reachability, trusted certificates, and rejection of unauthorized relay. Keep the generated configuration and passwords in a recoverable, restricted operations store; terminal history or a public issue is not a secret manager.