On 2022-01-25 6:56, Stephen J. Turnbull wrote:
nate writes:
It's "just worked" over the years, no issues. I have been using Linux since 1996, not a newbie here.
If so, and you're familiar with Docker (obviously not the same thing, but maybe? ;-), you might find the containerized version provided by Abhilash (which is usually quite up to date) closer to a turnkey installation. I use the venv approach myself (more because developer than out of principle), so I'm not really familiar with the container distribution, but from traffic on the list I get the impression that most of the troubles have to do with networking in containers, rather than configuring Django and WSGI hosts.
That is an interesting idea. I'm not much into docker but I certainly could do a LXC container or just another VM to run the older mailman and just not update it? My mailing lists are probably less than 1 message a month on average so real low usage.
I appreciate the detailed description of what you did and didn't find in the docs. The docs are weak on administration, we admit, and we we get some of those round tuits ....
Sure thing, I tried hard to be as polite as I could don't want to offend anyone with their hard work.
It's been years since we had an answer to that question. Mark might have more to say, but the last time we were challenged on this, the rival was Sympa, and the conclusion I came to was that the use cases are different.
I'll take a look at that thanks. I'd like to stick to mailman if I can though bypassing the distribution as was suggested to me to get a better version does worry me a bit from a maintainability standpoint, I try to keep things as clean as I can, and holy crap I was shocked at the number of dependencies the mailman3-full package pulled in(165 total packages that were not already installed, most were python3 related).
So bypassing that entirely does worry me a little, not that I run anything mission critical on my home server but my home server(that runs in a colo, so not really at home, I have 30 systems on my home network/colo network) historically is super low maintenance.
An extreme case I came across last year I discovered I was still using 2 RBLs in postfix that were shut down between 7 and 12 years ago! That just generated warnings in the postfix logs over the years but I wasn't paying attention(never hurt anything). Till I looked up the RBLs to see..wow, gone for that long, so I updated my postfix config! My postfix configs date back to ~2003 and have had minimal changes over the years, same goes for the rest of my mail system whether it was mailman, or Cyrus IMAP (barring a one time painful migration from Cyrus 1.x to 2.x).
Depending on your Linux distro, and your attitude to risk, Python 2 plus Mailman 2 in a container, VM, or even a dedicated host in the DMZ or outside the firewall might be a reasonable solution.
I will certainly consider that as an option, thanks!! Devuan 3.x still has mailman 2.1.29, in theory I could hack together a 2.1.39 Debian package to get it up to date in that respect.
nate