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.
Go to file
decentral1se 2f27f298f9
Remove duplicate hostnames with diabolical hack
2021-05-21 20:58:41 +02:00
.env.sample Attempt to share out mailu network 2021-05-17 00:38:58 +02:00
LICENSE Add placeholder 2020-10-07 10:43:34 +02:00
README.md Add relay net note 2021-05-21 20:08:01 +02:00
abra.sh Taking another run at packaging this thing 2021-05-08 18:26:32 +02:00
compose.yml Fix path 2021-05-21 14:59:07 +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
settings_local.py.tmpl Disable strict IP checks for internal IP 2021-05-21 17:21:17 +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.

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 on the mailman side and MAILMAN_CORE_NETWORK in the mailu config 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 on the mailu side)

More documentation coming after we recover from the diabolical hacking required to get this working.

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