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

Fix naming

This commit is contained in:
decentral1se 2021-05-21 17:37:29 +02:00
parent a1e0643677
commit a5932c9fb4
No known key found for this signature in database
GPG Key ID: 92DAD76BD9567B8A
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -4,15 +4,17 @@ A mailing list management system.
> https://docs.mailman3.org > https://docs.mailman3.org
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**. ## 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**.
This configuration assumes the following: This configuration assumes the following:
- you have a correctly configured mailu instance (e.g. `mail.example.com`) - 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 hostname, see following setups below for more on the shared network configuration) - 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 hostname, 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 an MX and an SPF record setup on your `lists.example.com` for incoming mail
- you have overlay networks configured for both your mailu and mailman 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 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 mailman and mailu stack which exposes the mailman generated aliases which can be fed into an 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) - you have a shared volume between your Mailman3 and Mailu stack which exposes the mailman generated aliases which can be fed into an 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. More documentation coming after we recover from the diabolical hacking required to get this working.