2f27f298f9 | ||
---|---|---|
.env.sample | ||
LICENSE | ||
README.md | ||
abra.sh | ||
compose.yml | ||
entrypoint.core.sh.tmpl | ||
entrypoint.web.sh.tmpl | ||
mailman-extra.cfg.tmpl | ||
nginx.conf.tmpl | ||
settings_local.py.tmpl |
README.md
mailman3
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 yourmailman-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
andSMTP_NETWORK
in the .env.sample on the mailman side andMAILMAN_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
- Set up Docker Swarm and
abra
- Deploy
coop-cloud/traefik
abra app new mailman3 --secrets
(optionally with--pass
if you'd like to save secrets inpass
)abra app YOURAPPDOMAIN config
- be sure to change$DOMAIN
to something that resolves to your Docker swarm boxabra app YOURAPPDOMAIN deploy
- Open the configured domain in your browser to finish set-up