Hi Charlie,
charlie derr 於 2023/8/26 19:43 寫道:
On 8/26/23 04:59, Franklin Weng wrote:
Hi,
After several times attempts I finally successfully build a (reliable enough) mailman3 instance on Debian.
I had a blog article describing how I did it. Maybe there were something you find it ridiculous, but they are all what I found important and may not be shown in the current documents.
https://blogs.slat.org/node/1012
Hope this helps.
Franklin
Thank you Franklin. And also of course, thank you to all the folks who work on and support mailman, as it's really wonderfully robust and excellent software.
TL;DR: we're interested in whether anyone has run into problems with mailman3 on debian bookworm.
Franklin, I'm curious as to why (at this point, with debian bookworm having been available for several months as the current stable platform) you wanted to do this. I'm asking specifically because the team I'm a part of has worked with mailman for many years (but not yet engaged with mailman3) as our main listserv answer for our users. We do have a need to spin up a new mailman instance soon, and we were planning on doing this with mailman3 on debian bookworm. If your choice to stick with bullseye was because of problems with trying to get things configured successfully on bookworm, we would definitely like to know any specific details which have created issues.
thanks so much in advance for any additional info, ~c
The problem was reported here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041681
AND here:
https://gitlab.com/mailman/django-mailman3/-/issues/68
Not sure which it should belong to. There are screenshots in the bug report, but some users said they couldn't open our Nextcloud instance. If you have problems opening the screenshots too you can give me a private mail I'll send pictures to you.
And - honestly I ran a mm3 instance on Debian Buster (10) a few years ago, and when I tried to upgrade my Buster to Bullseye the mm3 was totally broken. Fortunately I made a VM snapshot before upgrading so I reverted it back. However that instance was unstable too - it would run out of memory about every two weeks, so I had to setup a cron to reboot the VM every week. I have no idea what happened. It was pretty frustrated.
Then we moved all our services to another server hosts and I decided to rebuild the mm3 instances. I tried to build-remove-rebuild several times, including building it on Bullseye but got a lot of database locked errors, then tried it on Bookworm and got a broken django admin page, and finally set up a pretty stable instance on Bullseye which has run for about 6 weeks without any problem. So I decided to share the progress and what I found.
Hope it helps.
Franklin