[Mailman-Developers] [ mailman-Feature Requests-230429 ] Feature request: Single password for all lists

[noreply@sourceforge.net]

Feature Requests item #230429, was opened at 2001-01-29 22:59
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=350103&aid=230429&group_id=103

Category: (un)subscribing
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Matthew Saltzman (cumthsc)
Assigned to: Nobody/Anonymous (nobody)
Summary: Feature request: Single password for all lists

Initial Comment:
It would be a convenience for users that subscribe to several lists
on a single server if the same password worked for all lists subscribed
with a particular e-mail address.  I'd like the subscribe function to 
check for existence of the new subscriber's address on any other lists 
and take the password from there.  Of course, password changes
should propagate to all subscribed lists too.


----------------------------------------------------------------------

>Comment By: Barry Warsaw (bwarsaw)
Date: 2002-05-03 01:45

Message:
Logged In: YES 
user_id=12800

I'm going to close this because while the confederated
userdb is a MM3 design goal, in the meantime, in MM2.1 users
will be able to change their passwords for all lists
"globally".  It'll have the same effect.  The user will
still have to do a manual "change password globally" step
though.  That should be good enough for now.

----------------------------------------------------------------------

Comment By: Thomas Wouters (twouters)
Date: 2001-03-02 09:00

Message:
Logged In: YES 
user_id=34209

A separate userdb has been a longstanding feature request,
both from a lot of users as from Barry himself :) Moving to
feature requests. 

(Mental note: we should create tasks for all feature
requests, and just mark the repeating requests as closed.)


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2001-02-01 11:30

Message:
One of the items that has been on the planning bench for a long while (since I started using mailman in late '99, anyway) is to re-orient mailman's databasing scheme so that the subscriber info is abstracted into a separate "profile" DB.  Then the list DBS themselves would only contain references to the users profile DB entries instead of their real e-mail addresses.  Some of the benefits of this are:

-a user could opt to have a single password for all lists they are a member of
-if their e-mail address ever changes a user would only have to change it in one place
-would allow a user to unsubscribe from all lists at once.
-more information about each user could (optionally) be stored by mailman.
-would allow mailman to perform a little profiling about who is subscribed to what lists, etc.

Some of the downsides are (from my understanding anyway):
-would need to replace the DB system with a faster one, possibly even a third party one like MySql or something (which would complicate installation and setup a fair bit)
-would take a lot of re-coding (more than most want to do right now)
-introduces more possible stability problems and security holes.

Just my $.02...

~ Rick ~


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=350103&aid=230429&group_id=103