Re: [ext] Upgrading to mailman3 maybe?
Right, mailman 2 does not automatically prune archives, and I have used the prune script before, just curious if this was not a feature…
But I am also just checking to see what the advantages/disadvantages there are for going to mailman 3 over 2. Sure 2 is no longer being developed, BUT having said that our 2 environment is solid, and I understand it. I am a mailman admin, but not a full time Linux system admin, so Hyper kitty, Django, Virtualenv and all the other components of mailman 3 are not my forte. I have been playing around with just trying to stand up a mailman 3 in an isolated VM and not having much luck, and in searching around I am thinking mailman 3 is defiantly more of a commitment to get it installed/working at this time.
Bader, Robert (Bob) writes:
But I am also just checking to see what the advantages/disadvantages there are for going to mailman 3 over 2. Sure 2 is no longer being developed,
Neither is Python 2, which is far more worrying given that Mailman is an Internet-facing application. Among other things, I'm pretty sure the TLS protocols are not being updated. YMMV on that, but I advise you to check and think about your plans for the future. You wouldn't want to wake up one day and find that something doesn't work because Python 2 doesn't support a recent enough version of TLS or something. I'm not an expert on this, I'm just suggesting 15 minutes of paranoid Googling may save you an unpleasant surprise.
- Also in looking in the documentation states “Some configuration and settings aren’t available in Mailman 3’s UI yet,” is there a list of what is not available?
No, and it's a rapidly moving target anyway. Whatever list we give you now will (a) be invalid next week, and (b) not include some of the deficiencies in an early 2020 Mailman 3 that have since been implemented. Current releases have most of the settings people use as far as I know, especially in core. Postorius is a little behind, and HyperKitty is a completely different application from pipermail so I doubt a comparison would be meaningful.
- What OS have distro packages for Mailman 3 ready to go?
None, really. Debian and Fedora both have packages, but they are quite far behind the current release. They may be servicable for your purpose, but that's not something I can advise on without more information about your requirements and the version of Mailman that's in the distro-of-choice package.
Steve
On 3/23/21 8:45 AM, Bader, Robert (Bob) wrote:
Right, mailman 2 does not automatically prune archives, and I have used the prune script before, just curious if this was not a feature…
There is nothing currently planned or implemented, but a script to remove archived messages for --list older than --date shouldn't be too difficult to implement.
The tricky part is what to do about threads containing messages both older and newer than the cutoff. My MM 2.1 prune_arch script ignores this issue, but it makes sense to consider it for HyperKitty. Perhaps an option to a) delete the entire thread, b) keep the entire thread or c) delete the older messages from the thread would be in order, although maybe the a) option isn't needed.
But I am also just checking to see what the advantages/disadvantages there are for going to mailman 3 over 2. ...
Answered in Steve's reply.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Bader, Robert (Bob)
-
Mark Sapiro
-
Stephen J. Turnbull