Upgrade to MailMan 3.0! (or wait until 3.1 is out which supports migrating from 2.x)
Planned
Please expedite an upgrade to the new and vasty improved MailMan 3.0.
I like this idea 
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.
Hello. We are planning on delivering on this later this year (2024). I don't have an ETA yet, but work is scheduled to begin in April.
Hello. We are planning on delivering on this later this year (2024). I don't have an ETA yet, but work is scheduled to begin in April.
It says upgrades from 2 to 3 will be supported officially as of 3.1.
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:
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.
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.
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).
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.
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.
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.
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.
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:
From http://docs.mailman3.org/en/latest/pre-installation-guide.html
"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."
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:
From http://docs.mailman3.org/en/latest/pre-installation-guide.html
"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."
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.
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?
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?
Well, Mailman 3.2.1 was release on 22-Feb-2019. Has cPanel been able to make any progress with that version?
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://www.mail-archive.com/mailman-users@python.org/
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://www.mail-archive.com/mailman-users@python.org/
The Mailman upgrading page now says
The Mailman upgrading page now says
It's been 2 years since we got a 'Best Answer' from Benny regarding "...we remain interested in moving to Mailman 3.x once the migration process has stabilized and is reliable".
Mailman is now at version 3.3.3 and still cPanel rests with version 2.x
Hopefully we can have an update sometime in 2021...
It's been 2 years since we got a 'Best Answer' from Benny regarding "...we remain interested in moving to Mailman 3.x once the migration process has stabilized and is reliable".
Mailman is now at version 3.3.3 and still cPanel rests with version 2.x
Hopefully we can have an update sometime in 2021...
In any case, new accounts and lists could safely use MM 3.x.
In any case, new accounts and lists could safely use MM 3.x.
I was told a year or so ago by Mark Sapio not to expect a cpanel version of mm3 due to the more
stringent requirements (3 different programs working together). As a result it might be better to look at a
Combination forum and mailing list like flock and similar.
I was told a year or so ago by Mark Sapio not to expect a cpanel version of mm3 due to the more
stringent requirements (3 different programs working together). As a result it might be better to look at a
Combination forum and mailing list like flock and similar.
From the Mailman2 users list today, there appears to be a Python 3 port (alpha) for Mailman 2:
https://github.com/jaredmauch/mailman2-python3/
If this gets to a stable release it might be a lot easier for cPanel to offer than Mailman 3.
From the Mailman2 users list today, there appears to be a Python 3 port (alpha) for Mailman 2:
https://github.com/jaredmauch/mailman2-python3/
If this gets to a stable release it might be a lot easier for cPanel to offer than Mailman 3.
While I'm not hung up on version numbers or underlying technology, I'd really like to see cPanel integrate/migrate to a modern version of Mailman that has a future. The 2.X interface seems so unfriendly to administrators, so I'd hope any port of it would eventually get a UI/usability design that matches the expectations of this century, not stuck back in the 1980's.
I look how cPanel's UI continues to evolve, my hope is that the software platform can get to an evolved version of Mailman integrated into it.
While I'm not hung up on version numbers or underlying technology, I'd really like to see cPanel integrate/migrate to a modern version of Mailman that has a future. The 2.X interface seems so unfriendly to administrators, so I'd hope any port of it would eventually get a UI/usability design that matches the expectations of this century, not stuck back in the 1980's.
I look how cPanel's UI continues to evolve, my hope is that the software platform can get to an evolved version of Mailman integrated into it.
Insofar as this feature request has been open for eight years, and the last post from a cpanel staffer was five years ago, it seems pretty unlikely that cpanel will ever integrate Mailman 3.
Insofar as this feature request has been open for eight years, and the last post from a cpanel staffer was five years ago, it seems pretty unlikely that cpanel will ever integrate Mailman 3.
I can accept unlikely, but there should always be hope....
At least they have the 2.1.39 version in cPanel 110.0.8 (released in April 2023) which is what my hosting provider (and I) is using.
I can accept unlikely, but there should always be hope....
At least they have the 2.1.39 version in cPanel 110.0.8 (released in April 2023) which is what my hosting provider (and I) is using.
Hello. We are planning on delivering on this later this year (2024). I don't have an ETA yet, but work is scheduled to begin in April.
Hello. We are planning on delivering on this later this year (2024). I don't have an ETA yet, but work is scheduled to begin in April.
Replies have been locked on this page!