Please expedite an upgrade to the new and vasty improved MailMan 3.0.
Hey everyone! It looks like the updates we provided earlier this year were lost, so I'm adding them again.
We remain interested in moving to Mailman 3.x once the migration process has stabilized and is reliable. At the current time, the 3.x series is continuing to make progress in that area:
"How Can I upgrade from Mailman 2.1.x?Mailman 2.1 series is the current most popular series of Mailman. The short version is that as of now, upgrading from Mailman 2.1 to Mailman 3.1 is buggy."
It says upgrades from 2 to 3 will be supported officially as of 3.1.
I like the idea, but I would not want to roll this out until upgrades are officially supported to take customers from 2.1 to 3.0. Per Mailman wiki:
Surprisingly, I did not find the 3.1 migration target mentioned in the 3.1 milestone. It is, however, mentioned on the 3.0 wiki page.
On the MM discussion list this is a topic of concern for many. There is a team working on a migration process however they are under the impression that cPanel has a modified MM structure so that their migration may not work in a cPanel environment. It may be the case that cPanel has to develop the migration for their use in house. Commenst by the cPanel team would be good at this point.
The Mailman developers are suggesting Mailman 3 for new lists. I think Cpanel should offer a Mailman 3 standalone install. Administrators should be able to pick the latest 2.x release or the current 3.x release (presumably they do not co-exist).
Also looking forward to this new version integrated into cPanel as the current version is way to old and lack of new features.
I agree with Dean Suhr that letting site admins choose between Mailman 2.[latest] and Mailman 3 is the best option by far. According to https://wiki.list.org/Mailman3 it should be possible to run them in parallel.
As no-one knows when 3.1 might arrive, it's a bit too much of a wait for those of us aching to make the switch, otherwise.
After two long years Mailman 3.1 has finally been released! To give some perspective on how things are likely to go internally: It's been added to our discussion list for our next version planning (the list for version 70, which we'll go into in a few months). Once we do, there'll be an internal evaluation period (we've got a ton of mailing lists on our mail servers, so it'll get a ton of real-world use) and a lot of testing to be done. Once there's actual motion on it internally I'll be back to provide everyone with an update.
Very excited to hear this. Will be keeping a close eye on this page.
Right now I am not holding my breath based on the v3.1 pre-installation guide.http://docs.mailman3.org/en/latest/pre-installation-guide.html#how-can-i-upgrade-from-mailman-2-1-x
How Can I upgrade from Mailman 2.1.x?Mailman 2.1 series is the current most popular series of Mailman. The short version is that as of now, upgrading from Mailman 2.1 to Mailman 3.1 is buggy.
Now the long version. Because of the changes in Database Schema, migrating from Mailman 2.1 to Mailman 3.1 is not very easy, though it can be done with some scripting. We are working on it and it should be working soon, we don’t have an exact timeline on it though.
Archives however can be imported into Hyperkitty easily, however URLs to attachments are going to break because the URL paths are different in Hyperkitty. Although, You might be able to retain your HTML archives from Mailman 2.1 and continue archiving newer emails in Hyperkitty.
My users hate MM 2 because the Archives do not work well for finding old posts. I suggested Slack or Flock but these do not easily allow forced membership in all topics for the free versions. My members MUST be able to see and post in all topics by default.
I suggested a WordPress forum, but they don't like to go "'outside" of email.
So MM3 seems perfect. their archives are clearly shown by topics with excerpts. Ione problem that remains is people changing the topic and creating a second set of messages. I suppose as admin i could force them to post in a given topic or open a new topic for only new things. Not sure. But it is for this reason I await MM3.
It looks like there might be some progress. The Mailman folks have a 2.1 to 3 migration guide here, and they are on v3.2. Is it time for a cPanel migration tool?
Well, Mailman 3.2.1 was release on 22-Feb-2019. Has cPanel been able to make any progress with that version?
Unfortunately, the upgrade process is still buggy and is not something cPanel can support at this time. We’re hoping to work with the Mailman folks at some point in the future to accomplish this goal.
Can you support a migration with NO archives?
That’s certainly one potential solution, but we won’t know implementation details until we get into it.
Thanks for the prompt reply. I’m looking at deploying a new listserve, so an upgrade/migration process isn’t necessary, just an install and go from there.
There's an interesting discussion right now on the Mailman 2 list (Mailman-Users@python.org). One aspect is an effort to develop a better (simpler, e.g. Django-free) UI for Mailman 3. Another has to do with whether Mailman 2 should be updated to work with Python 3. I suspect your developers follow that list but if not look for the thread "The last release from the GNU Mailman project" at https://firstname.lastname@example.org/
Replies have been locked on this page!
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer
software that facilitates the management and configuration of Internet web servers.