Issues with migrating from Mailman2 to Mailman 3
Hello all,
I'm currently trying to convert a Debian based mailman2 installation to a docker based mailman3 installation. I successfully running the mailman-web and mailman-core containers together with the database container but I'm struggling with the import of the old mailing lists. In the core container I'm running this two commands for every mailing list:
mailman create mailman@example.com mailman import21 mailman@example.com /oldmailman/lists/mailman/config.pck
Then I'm switching over to the mailman-web container and running this two commands:
python3.6 manage.py hyperkitty_import -l mailman@example.com /oldmailman/archives/private/mailman.mbox/mailman.mbox python3.6 manage.py update_index_one_list mailman@example.com
I'm getting no errors or something else which could indicate a problem. After that I'm looking into the web interface http://example.com/postorius/lists/ There I can only see the public mailing list and the private ones are not shown there (as expected). When I then try to login with the List Manager credentials of the lists (from mailman2) I can't login in. So I thought maybe I have to "register" myself again to than get access to the list management. So I tried that but when I filled out the form and click "Register" I'm presented with an error page which titles "Serverfehler" (Server error in german) and the message "An error occurred while processing your request."
When I then go back a step and try to register again I got the error message that the username is already taken. When I then try to login I can't login I always get the "An error occurred while processing your request." page.
Does anyone have an idea what point I'm missing?
-- With best Regards Uwe Grasshoff
On 9/22/19 10:29 AM, Uwe Grasshoff wrote:
Hello all,
I'm currently trying to convert a Debian based mailman2 installation to a docker based mailman3 installation. I successfully running the mailman-web and mailman-core containers together with the database container but I'm struggling with the import of the old mailing lists. In the core container I'm running this two commands for every mailing list:
mailman create mailman@example.com mailman import21 mailman@example.com /oldmailman/lists/mailman/config.pck
Then I'm switching over to the mailman-web container and running this two commands:
python3.6 manage.py hyperkitty_import -l mailman@example.com /oldmailman/archives/private/mailman.mbox/mailman.mbox python3.6 manage.py update_index_one_list mailman@example.com
I'm getting no errors or something else which could indicate a problem. After that I'm looking into the web interface http://example.com/postorius/lists/ There I can only see the public mailing list and the private ones are not shown there (as expected).
Everything up to this point is expected behavior.
When I then try to login with the List Manager credentials of the lists (from mailman2) I can't login in. So I thought maybe I have to "register" myself again to than get access to the list management. So I tried that but when I filled out the form and click "Register" I'm presented with an error page which titles "Serverfehler" (Server error in german) and the message "An error occurred while processing your request."
I'm not sure about the error, but the import21 process registered you so what you need to do is go to the Login page, click "Forgot Password?" and then request a password reset.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi,
I'm not sure about the error, but the import21 process registered you so what you need to do is go to the Login page, click "Forgot Password?" and then request a password reset.
The reset also failed with the error message that okay I have finished a few more steps on the way to containerized mailman ;-)
The mailman-web container also needs the environment variables which tells mailman-core to use postfix on an other host for delvery.
But still I can't recover a password. It always tells me "Diese E-Mail-Adresse ist keinem Konto zugeordnet" which means "This e-mail address is not assigned to any account". But when I now register I can see all the lists which I'm assigned to. So basically my problem was the missing environment variables
- MTA=postfix - SMTP_HOST=mail I though it's only needed for the core container but they also need to be assigned to the web container.
With best Regards Uwe Grasshoff
participants (2)
-
Mark Sapiro
-
Uwe Grasshoff