Install mailcow as an integrated Compose mail suite

mailcow is a multi-component Docker Compose mail/groupware suite. Its resource, networking, and DNS prerequisites matter before the web UI becomes available; it is not just a Postfix image with a dashboard.

For the comparison with lighter stacks and single-binary servers, see mailcow in our Linux mail-server comparison.

Prepare the supported stack

1. Follow mailcow’s official system prerequisites and DNS setup, then use its installation instructions for the current deployment commands.
2. Check port conflicts, stable addressing/PTR, storage capacity, container networking, and the documented firewall behavior.
3. Obtain the supported repository/release and generate the deployment’s configuration with its provided tooling.
4. Review the hostname, TLS/ACME setup, persistent volumes, and administrative access before starting public services.

Use mailcow-supported override/configuration mechanisms. Editing generated service configuration inside a container may be overwritten and can bypass the suite’s management model.

Validate before moving domains

Check service health and logs across the suite, not only Nginx. Secure the administrative account and create one controlled domain/mailbox. Verify receipt, authenticated sending, client access, and rejection of unauthorized relay.

Preserve existing production MX until the selected services and backups are ready. Optional webmail/groupware behavior must be tested with actual clients; successful SMTP does not demonstrate calendar synchronization or every groupware feature. Keep credentials and full configuration output out of shared support logs.