Mailman 3 November 2002 - Mailman-Developers

Re: [Mailman-Developers] More extend.py questions
by Martin Whinnery <martin.whinnery＠sbc.ac.uk> Nov. 1, 2002

Nov. 1, 2002

On Wed, 30 Oct 2002, Greg Ward wrote: > On 30 October 2002, Martin Whinnery said: > > Please indulge a python virgin. Barry has advised someone to 'overload > > the Load & Save function' in extend.py . Would someone help me with a > > little sample? It doesn't need to do anything useful, just replace the > > original function. > > Huh? There's no file called extend.py in the Mailman source tree. Just > what are you trying to accomplish? > And I quote (From NEWS 2.36) " - Membership Adaptors o Internally, mailing list memberships are accessed through a MemberAdaptor interface. This would allow for integrating membership databases with external sources (e.g. Zope or LDAP), although the only MemberAdaptor currently implemented is a "classic" adaptor which stores the membership information on the MailList object. ... - List Extensibility o A framework has been added which can be used to specialize and extend specific mailing lists. If there is a file called lists/<yourlist>/extend.py, it is execfile()'d after the MailList object is instantiated. The file should contain a function extend() which will be called with the MailList instance... " Now after a little more digging (And I take your point about not hacking the actual source, I don't know what I was thinking. Probably why I'm 'just the assistant') it appears that what I need to do is implement new Load() and Save() functions ( orginally defined in MailList.py ), which cause membership information to be read into the mlist structure from LDAP rather than from config.pck, and which fail to write that information back to config.pck. Or rather, (after more digging), Save() should remove all the membership information from the MailList instance before calling the original Save(), and Load should call the original Load() then replace any membership information with info taken from LDAP. I appreciate that this will leave membership options unable to be changed, but that's what we want. A later version might be able to write that info back to LDAP, but there's authentication issues and the matter of schema definitions, and I don't need to go there just yet. Now, what I want is for the Load() and Save() functions defined in MailList.py to be overridden for this list with my own versions. I just don't understand Python/Mailman well enough. --------- My efforts so far ------------- # /usr/local/mailman/lists/ldaplist/extend.py def extend(mlist): mlist.OldSave = mlist.Save def MySave(self): print "WOOKIE" # So I can see it in withlist mlist.__class__.Save(self) mlist.Save = MySave -------- snip snip ---------------------- But when I try m.Save(m) from within "withlist ldaplist", I get a 'NotLocked' error: NotLockedError: <LockFile 137391332: /usr/local/mailman/locks/ldaplist.lock [unlocked: 18000sec] pid=9172>: None And at this point I'm pretty well stuck. Any examples, flames, advice or witticisms will be revered in a darkened room. Thanks in advance (I like the desperate sound that makes when I say it) Martin Whinnery "Just the" Assistant Network Manager South Birmingham College

1 0

Re: [Mailman-Developers] Help programming MemberAdaptor...
by Martin Whinnery <martin.whinnery＠sbc.ac.uk> Nov. 1, 2002

Nov. 1, 2002

On Wed, 30 Oct 2002, Greg Ward wrote: > > What I'd really like to do is have lists EITHER populate in the normal > > file way OR populated from LDAP. I was thinking I might use an address > > like > > Err, define "populate". Is this a one-time thing? Or do you want the > list membership to always come from an LDAP lookup? > The latter. I help run a large educational campus, and we hold all accounts and groups in LDAP. These groups change membership over time, and I want to associate mailing lists with some of them. What I don't need is the headache of remembering to keep the memberships in sync. > If the former, I would just write a script that does the LDAP query and > sets the list population from it. Use bin/add_members as an example. > If we absolutely must. It's what we do with DNS and DHCP. But I'd rather not. Just more code to maintain. > If the latter, why use Mailman at all? Why not just use an MTA that can > lookup aliases using LDAP, and then send mail to that alias? I'm pretty > sure both Exim and postfix can do that. > 'Cos mailman does the [approve|reject|defer|discard] thing. And archives. And it deals with 'real' mailing lists (which we would die rather than lose). Martin Whinnery *Assistant* Network Manager South Birmingham College 'Just the assistant'

1 0

python.org mailing list memberships reminder (fwd)
by Dale Newfield Nov. 1, 2002

Nov. 1, 2002

I'm guessing from this (and the settings I've got on these lists) that setting the "Get password reminder email for this list?" flag to "No" doesn't work. -Dale ---------- Forwarded message ---------- Date: Fri, 01 Nov 2002 05:00:22 -0500 From: mailman-21-owner(a)python.org To: Dale(a)newfield.org Subject: python.org mailing list memberships reminder This is a reminder, sent out once a month, about your python.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list.

1 0