User account issue after importing data from Mailman 2.x server
We finally migrated from Mailman 2.x to a Mailman 3.x several months ago. We have had some issues with people who are active list members not being able to login with their user creds and when trying to use the 'Forgot Password' link to reset, being told their user account does not exist. They can submit email to the list and get copied on other list traffic.
I just started looking at a user and a list in both the Postorius and Django admin web UIs and found:
in Postorius:
- list exists, has 20K plus subscribed members and has 3 list owners
- user exists and is subscribed to this list
in Django:
- in HyperKitty section
- in the Mailing lists page, the list exists, no idea about members BUT it has 147 owners (also the same 147 moderators)
- in the Emails page, there are 149K plus entries
- in the Profiles page, there are 147 entries
- in the Accounts->Email addresses page, there are only 155 entries
- in the AUTHENTICATION AND AUTHORIZATION->Users page, there are 147 entries
- in HyperKitty section
Should Mailman 3.x have created user accounts for everyone when importing the data from the old server?
To correct the issue on a case by case basis, can I as a server admin do something via the web UI or CLI or do we need to remove the email address from the list and ask the person to create a new account using that address and to resubscribe to the specific list or other?
Thanks, David Goldsmith
On 10/24/24 11:01, dgoldsmith--- via Mailman-users wrote:
We finally migrated from Mailman 2.x to a Mailman 3.x several months ago. We have had some issues with people who are active list members not being able to login with their user creds and when trying to use the 'Forgot Password' link to reset, being told their user account does not exist. They can submit email to the list and get copied on other list traffic.
Mailman's import21 process creates Mailman users for the list
memberships, but it does not create the Django user used for access to
HyperKitty and Pustorius. Your users can't reset their Django (web UI)
login password because they don't have a Django account. They need to
Sign up rather than Sign in.
Should Mailman 3.x have created user accounts for everyone when importing the data from the old server?
It did create Mailman users, but these have nothing to do with the users that can log min to the web UI. It doesn't create these Django users.
To correct the issue on a case by case basis, can I as a server admin do something via the web UI or CLI or do we need to remove the email address from the list and ask the person to create a new account using that address and to resubscribe to the specific list or other?
Just tell the users to go to the web UI and Sign up rather than Sign in. Removing and resubscribing a user will not help. The users that are
members of mailing lists are completely separate from the users that can
log in to the web UI. This is in part due to the modular nature of
Mailman 3 and the fact that a Mailman 3 installation doesn't necessarily
even have a Django based web UI.
You may also be interested in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/T...
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
dgoldsmith＠sans.org -
Mark Sapiro