Re: [Mailman-Developers] Mailman and Extend.py
Mark Sapiro wrote:
C Nulk wrote:
Thank you for responding. A quick question, will MM3 also support the @list funtionality, both for the 4 *_these_nonmembers options and the owner, moderator, and the ban_list options?
I have a few remarks about this. The @listname feature was implemented in Mailman 2.1/2.2 after they diverged from 3.0 so it's not in 3.0 at this moment. It probably will be if it makes sense to do so.
Thank you for the info Mark.
However, for your situation, the whole notion of a member adaptor per se goes away in 3.0 and is replaced by the backend database interface, so this may not be that significant.
Okay. I understand.
Regarding owner and moderator, my understanding (Barry will correct me) is that these roles are defined in the back-end rather than being list attributes per se so I think your question becomes moot at least for owner and moderator.
Don't have a problem with a backend database for deriving/managing the members of a list, whether it be MySQL, Postgresql, LDAP, or anything else. Clearly makes sense to me.
It was just for the other "list of email addresses" options I was curious about. If they are defined by a backend database, am I restricted to the same backend database as I am using for members list? Or, can I use a different backend for each of the "list of email addresses" options whether it be LDAP, MySQL, Postgresql, etc. or any combination of the mix?
Now, about an LDAP interface to MM3 (or possibly making the MM2 more complete), is anyone interested in what ideas I have thought about? If so, a new thread should probably be started.
Thanks, Chris
On Apr 17, 2009, at 12:53 PM, Chris Nulk wrote:
It was just for the other "list of email addresses" options I was curious about. If they are defined by a backend database, am I restricted to the same backend database as I am using for members
list? Or, can I use a different backend for each of the "list of email addresses" options whether it be LDAP, MySQL, Postgresql, etc. or any combination of the mix?
In thinking about this a bit more, for MM3, you might in fact be able
to get away with just re-implementing the roster layer. It's rosters
that tell mailing lists two important facts: 1) who gets to post to a
mailing list and 2) who gets delivery of posted messages. Rosters are
really just queries, they have no persistent storage themselves. So
while I still think it would take some clever programming, it should
be possible to keep user information in the RDBMS and provide for
subscription information by LDAP.
Now, about an LDAP interface to MM3 (or possibly making the MM2 more complete), is anyone interested in what ideas I have thought about?
If so, a new thread should probably be started.
Sure, I'd like to hear it because I think this will be an interesting
use case.
-Barry
Barry Warsaw wrote:
On Apr 17, 2009, at 12:53 PM, Chris Nulk wrote:
It was just for the other "list of email addresses" options I was curious about. If they are defined by a backend database, am I restricted to the same backend database as I am using for members list? Or, can I use a different backend for each of the "list of email addresses" options whether it be LDAP, MySQL, Postgresql, etc. or any combination of the mix?
In thinking about this a bit more, for MM3, you might in fact be able to get away with just re-implementing the roster layer. It's rosters that tell mailing lists two important facts: 1) who gets to post to a mailing list and 2) who gets delivery of posted messages. Rosters are really just queries, they have no persistent storage themselves. So while I still think it would take some clever programming, it should be possible to keep user information in the RDBMS and provide for subscription information by LDAP.
Now, about an LDAP interface to MM3 (or possibly making the MM2 more complete), is anyone interested in what ideas I have thought about? If so, a new thread should probably be started.
Sure, I'd like to hear it because I think this will be an interesting use case.
Great. I will start the new thread next week. I will need a little time to compose the ideas. Hopefully, if the ideas make sense, they can be applied to MM3 and MM2.
Thanks for your help Barry and Mark,
Chris
participants (3)
-
Barry Warsaw -
C Nulk -
Chris Nulk