Hello,
Some of us at opendev.org are looking to migrate to mailman 3 for our
list servers. We've got about 98% of things sorted out using maxking's
docker images (thank you for publishing those along with excellent
documentation). There are however a small number of things that we've
run into that we'd like to address before we take this to production.
* Mailman 3 relies on lynx to convert html email to txt email. Lynx
isn't currently installed in the docker images, but I've pushed a PR
to add it to the images.
https://github.com/maxking/docker-mailman/pull/552
* There are some user and group inconsistencies between the images. Not
a deal breaker, but would be good to understand if these are
intentional or if they can be changed without massively impacting
people.
https://github.com/maxking/docker-mailman/issues/550
* Issues with ALLOWED_HOSTS settings making assumptions about the
environment and its inputs. We've worked around these by bind mounting
in our own settings.py with these problems addressed, but it would be
good to address them in case anyone else has run into this too.
Details in these github issues:
https://github.com/maxking/docker-mailman/issues/548https://github.com/maxking/docker-mailman/issues/549
Ideally we'd avoid forking the images downstream and modifying them
ourselves, but it seems the docker image repo is not getting a ton of
attention recently. Totally understand that this may not be the biggest
priority. We're happy to help address these by writing fixes and sending
pull requests, but guidance would be appreciated before we head too far
down that road.
Once again thank you for the great documentation and images. They have
already gotten us most of the way to production and the issues we've
found are relatively minor.
Clark
