Copy mailman settings and subscribers

edmcdonagh

Registered
Oct 29, 2017
1
0
1
Ruislip
cPanel Access Level
Reseller Owner
I have a reseller account. My provider recently moved my reseller account from an old server (old PHP/Perl etc) to a newer one (by mutual agreement!). Both are cPanel.

On the new server, the mailing lists continued to function normally, until someone needed to moderate something.

Going to the URL http://mydomain.tld/mailman/admindb/discuss_mydomain.tld leads to the following error once you try to log in:

Bug in Mailman version 2.1.23 We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs.​

However, if you go via cPanel to manage the list, everything works. This uses a URL like https://myprovider.tld:2083/cpsess0123456789/3rdparty/mailman/admin/discuss_mydomain.tld/

My provider tells me that they have corrected any file permission errors on the new server, and it all should work. The only remaining remedy I am told is to create a new list and copy the archives over. As the lists cannot be renamed, the existing list needs to be deleted before the new one is created.

A new list that has been created as a test, with a copy of one of the lists archives, shows that the new list seems to work.

However, they tell me that there is no way to copy the subscribers and their settings or any of the other configuration.

Is this the case on a cPanel/WHM setup, or could there be some tools that they are not aware of that I could point them to?

I would very much appreciate any assistance you may be able to offer.

  • CENTOS 7.4 standard
  • v66.0.26
Ed
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,880
2,258
463
The only remaining remedy I am told is to create a new list and copy the archives over. As the lists cannot be renamed, the existing list needs to be deleted before the new one is created.
Hello,

Could you have them review the thread linked below to see if the referenced solution helps?

Bug in Mailman version 2.1.23

Thank you.