This configuration is intended to be used with a [Mailu](https://git.autonomic.zone/coop-cloud/mailu) instance which is setup **on the same VPS**. A shared volume (Mailman core generated aliases for mail delivery) and a shared network (Mailu and Mailman can then see each other) are used to ensure that the postfix service in the Mailu stack can handle incoming and outgoing mail for Mailman.
- a working Mailu instance (e.g. `mail.example.com`)
- a MX and SPF domain record for your mailing list domain (e.g. `lists.example.com`) ponting to your Mailu instance for incoming mail (e.g. `mail.example.com`)
- the `mailman-core` container IP range configured in the `RELAYNETS` environment variable on the Mailu side for outgoing mail relaying (ensure you do not an open relay using a tool like [mxtoolbox](https://mxtoolbox.com))
- overlay networks configured for both the Mailu and Mailman3 stacks (see `SMTP_HOST` and `SMTP_NETWORK` in the [.env.sample](./.env.sample) and `MAILMAN_CORE_NETWORK` [in the Mailu config](https://git.autonomic.zone/coop-cloud/mailu/src/branch/main/.env.sample))
- a shared volume between your Mailman3 and Mailu stack which exposes the Mailman generated aliases to Mailu (see `MAILMAN_CORE_VOLUME` [in the mailu config](https://git.autonomic.zone/coop-cloud/mailu/src/branch/main/.env.sample))