coop-cloud/mailman3
coop-cloud
/
mailman3
Archived
1
0
Fork 0
Code Issues 5 Pull Requests Releases Wiki Activity
A mailing list management system
This repository has been archived on 2021-07-22. You can view files and clone it, but cannot push or open issues or pull requests.
75 Commits 1 Branch 0 Tags 118 KiB
Shell 100%
Go to file
decentral1se eec9762dac
Revert internal network change (see coop-cloud/organising#62) 		2021-07-15 16:07:36 +02:00
.drone.yml Remove trigger, we make the tags [ci skip] 2021-06-04 00:14:49 +02:00
.env.sample Allow to disable signup 2021-05-23 13:00:28 +02:00
LICENSE Add placeholder 2020-10-07 10:43:34 +02:00
README.md Try to trim up that documentation once again 2021-05-23 12:20:38 +02:00
abra.sh Allow to disable signup 2021-05-23 13:00:28 +02:00
compose.yml Revert internal network change (see coop-cloud/organising#62) 2021-07-15 16:07:36 +02:00
entrypoint.core.sh.tmpl Remove duplicate hostnames with diabolical hack 2021-05-21 20:58:41 +02:00
entrypoint.web.sh.tmpl Add missing env var 2021-05-14 16:57:09 +02:00
mailman-extra.cfg.tmpl Use the right env vars 2021-05-14 15:47:36 +02:00
nginx.conf.tmpl Use new service name 2021-05-16 15:02:25 +02:00
renovate.json Add renovate.json 2021-06-04 07:02:39 +00:00
settings_local.py.tmpl Allow to disable signup 2021-05-23 13:00:28 +02:00

README.md

mailman3

https://docs.mailman3.org

A mailing list management system.

  • Category:
  • Status:
  • Image: maxking/mailman-*
  • Healthcheck:
  • Backups:
  • Email:
  • Tests:
  • SSO:

Mailu integration

This configuration is intended to be used with a 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:

  • 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)
  • overlay networks configured for both the Mailu and Mailman3 stacks (see SMTP_HOST and SMTP_NETWORK in the .env.sample and MAILMAN_CORE_NETWORK in the Mailu config)
  • 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)

Basic usage

  1. Set up Docker Swarm and abra
  2. Deploy coop-cloud/traefik
  3. abra app new mailman3 --secrets (optionally with --pass if you'd like to save secrets in pass)
  4. abra app YOURAPPDOMAIN config - be sure to change $DOMAIN to something that resolves to your Docker swarm box
  5. abra app YOURAPPDOMAIN deploy
  6. Open the configured domain in your browser to finish set-up