On 10/20/20 6:54 AM, Brian Carpenter wrote:
On 10/19/20 11:32 PM, Mark Sapiro wrote:
Mailman 3 is totally different from Mailman 2.1 in this respect. Mailman 2.1 had no concept of user. All it knew was addresses subscribed to lists and an address subscribed to one list had no connection to the same address subscribed to another list or being an owner or moderator of a list.
I think this should still be the case for non-registered list members. List owners/moderators are different. They HAVE to be registered users of Postorius/Affinity in order to manage/moderate a list.
Here's a thought. For Affinity/Empathy at least, how about using Mailman core's user as the Affinity registered user. I.e., if someone's first interaction is to register with Affinity, have that registration create a core user to keep the Affinity registration data. This core user already accommodates a display_name and password and email address(es).
If the person already is a core user when registering for Affinity, just update the core user as needed, probably only a password reset or just setting it if it is currently None.
Then you don't have the issue of another, separate registration for Affinity.
This would be more difficult for Postorius/Hyperkitty because those users are Django users, but that isn't an issue for Affinity.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan