Dear MM3 list,
while doing some reboot proofing for our mailman setup, I once more ran into https://github.com/maxking/docker-mailman/issues/133. May it be that https://github.com/maxking/docker-mailman/pull/143 hasn't made it yet into the docker image maxking/mailman-web:0.2 which is the current recommended stable version?
Would be real nice (for stability!) to have this feature included.
Best regards,
Johannes Winter
On Tue, Jan 22, 2019, at 9:01 AM, Johannes Winter wrote:
Dear MM3 list,
while doing some reboot proofing for our mailman setup, I once more ran into https://github.com/maxking/docker-mailman/issues/133. May it be that https://github.com/maxking/docker-mailman/pull/143 hasn't made it yet into the docker image maxking/mailman-web:0.2 which is the current recommended stable version?
I think I messed up and forgot to tag 0.2 in the repo, so I am not sure if that commit was included in 0.2 release.
I need to figure out some more automation for the tagged releases. Anyway, I'd recommend that you set your IP address for Mailman Core manually, if you can. That should avoid having that issue.
Eventually, there will be no IP addresses and thing, you can see my WIP MR to remove all the hard coded addresses1.
Would be real nice (for stability!) to have this feature included.
Best regards,
Johannes Winter
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
participants (2)
-
Abhilash Raj
-
Johannes Winter