Prepare a supported Mail-in-a-Box appliance host

Mail-in-a-Box is intentionally opinionated. Start with a clean supported host, not a machine containing a production website, another mail stack, or an operating-system version selected from an old tutorial.

Before committing to the appliance model, compare Mail-in-a-Box with other Linux mail servers.

Complete the preflight

1. Use the current setup guide to select the supported Ubuntu release and machine requirements.
2. Confirm public addressing, permitted port 25, reverse DNS, and the intended appliance hostname.
3. Plan domain/DNS ownership, including nameserver/glue requirements when delegating DNS to the appliance.
4. Review the installer source/instructions before executing a privileged installation; keep an independent access and rollback path.

The guide explains that the appliance prefers managing DNS so it can maintain its required records. Decide how an existing website or other services retain their records before changing nameservers.

Verify the installed appliance

Protect the administrative login, check the status console’s system/DNS findings, and confirm certificates use the intended hostnames. Create only a controlled mailbox initially.

Do not treat an installer success as evidence that every DNS delegation, client connection, or outbound IP reputation issue is solved. Keep existing mailbox routing until tests pass. Arbitrary component overrides may be replaced or break on upgrades; if deep customization is required, reconsider the appliance fit rather than maintaining an undocumented fork of its configuration.