Stops sending emails after rebooting the docker host about mailman2 HOT 3 CLOSED

Hi, Thx for reporting this... usually prod servers are quite stable and as we schedule to destroy containers on a regular basis to replace them with new ones so that we are close to immutability, we never encountered this issue before.
BTW, this container declares volumes for important data (lists, archives, tls cert...) so they won't disappear after container replacement.
But you are right, a graceful stop of the processes in this container while a "docker stop" is asked is consistent (containers are too often maltreated as they are replaceable) and it would fix immediately this stop/start issue in case of a server reboot so that it won't have to wait a container replacement to be fixed.
The "docker stop" command sends an initial SIGTERM signal to PID1 and if no termination happens during the defined grace period it kills them with a SIGKILL. As this container was conceived rather like a convenient mailing list tools deployment than a standard functional container the PID1 is given to the run.sh start script that runs several services and indeed doesn't transmit, for now, the termination signal to the services started.

So I'm gonna add a few lines ASAP to the run.sh script to stop the services properly when a SIGTERM is received.
I'll tell you when the updated script is pushed so that you can pull the new d3fk/mailman2:latest container version.

from mailman2.

The new version of the run.sh script has now been pushed and the container automatically built by Docker Hub ... a simple docker pull d3fk/mailman2 before deploying a new mailman container should fix this issue on your next server reboot or container stop/start cycle.

from mailman2.

Your fix has worked excellently. Thank you very much! :-)

from mailman2.