coop-cloud/mailman3
coop-cloud
/
mailman3
Archived
1
0
Fork 0
Code Issues 5 Pull Requests Releases Wiki Activity

Try to trim up that documentation once again

This commit is contained in:
decentral1se 2021-05-23 12:20:38 +02:00
parent fe601c1d2f
commit 0074a84e44
Signed by: decentral1se
GPG Key ID: 92DAD76BD9567B8A
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -19,17 +19,15 @@ A mailing list management system.
## Mailu integration
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**. The two configurations for Mailu and Mailman remain separate however. We use shared networks and volumes to share configuration between the two stacks. The hope is that it will be easier to manage them as separate configurations. This is very much an experiment.
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.
This configuration assumes the following:
- you have a correctly configured Mailu instance (e.g. `mail.example.com`)
- 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)
More documentation coming after we recover from the diabolical hacking required to get this working.
- 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))
## Basic usage