From fca03b471e53f2f4e1300184ee04aa27342ebca2 Mon Sep 17 00:00:00 2001 From: decentral1se Date: Fri, 21 May 2021 20:08:01 +0200 Subject: [PATCH] Add relay net note --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index adb86af..84d3f28 100644 --- a/README.md +++ b/README.md @@ -26,6 +26,7 @@ This configuration assumes the following: - you have a correctly configured Mailu instance (e.g. `mail.example.com`) - you have a relay domain setup on your Mailu side which relays mails (e.g. `lists.example.com` and the remote host is your `mailman-core` service name (e.g. `my_stack_core`), see following setups below for more on the shared network configuration) - you have an MX and an SPF record setup on your `lists.example.com` for incoming mail +- you have your Mailman container network configured in the `RELAYNETS` environment variable on the Mailu side for outgoing mail - you have overlay networks configured for both your Mailu and Mailman3 stacks (see `SMTP_HOST` and `SMTP_NETWORK` in the [.env.sample](./.env.sample) on the mailman side and `MAILMAN_CORE_NETWORK` [in the mailu config](https://git.autonomic.zone/coop-cloud/mailu/src/branch/main/.env.sample) on the mailu side) - you have a shared volume between your Mailman3 and Mailu stack which exposes the mailman generated aliases which can be fed into a postfix override on the mailu side (see `MAILMAN_CORE_VOLUME` [in the mailu config](https://git.autonomic.zone/coop-cloud/mailu/src/branch/main/.env.sample) on the mailu side)