Hi,
Here at the University of Adelaide we have several very large lists that are generated by ldap queries. A module offered to us by Karl A. Krueger at the Woods hole Oceanographic Institute works a treat, and generates the lists based on ldap search criteria.
What we wish to do now is restrict who can send to the list without moderator intervention. Take for example the all student list here, currently we have another ldap entry which authorises posting to this list.
My question is where in the current Mailman code ( v2.1.5 ) can we place some code to check this ldap authorisation entry?
Cheers
-- Jeffrey Borkent Systems Specialist Information Technology Services University of AdelaideKarl A. Krueger Level 7, 10 Pultney Street Adelaide. 5005 Ph: 8303 3000 jeffrey.borkent@adelaide.edu.au
CRICOS Provider Number 00123M
This email message is intended only for the addressee(s) and contains information that may be confidential and/or copyright. If you are not the intended recipient please notify the sender by reply email and immediately delete this email. Use, disclosure or reproduction of this email by anyone other than the intended recipient(s) is strictly prohibited. No representation is made that this email or any attachments are free of viruses. Virus scanning is recommended and is the responsibility of the recipient.
Jeffrey Borkent wrote:
Here at the University of Adelaide we have several very large lists that are generated by ldap queries. A module offered to us by Karl A. Krueger at the Woods hole Oceanographic Institute works a treat, and generates the lists based on ldap search criteria.
Presumably, this is a Member Adaptor module
What we wish to do now is restrict who can send to the list without moderator intervention. Take for example the all student list here, currently we have another ldap entry which authorises posting to this list.
My question is where in the current Mailman code ( v2.1.5 ) can we place some code to check this ldap authorisation entry?
Whatever Member Adaptor is in use for a list defines a function getMemberOptions(self, member, flag) in that module. In your case, this should be in the module referred to above. You need to arrange that whenever this is called with flag = mm_cfg.Moderate, it returns True (or 1) if member should be moderated and False (or 0) if member should not be moderated.
I.e. you need to place your code in getMemberOptions() in your Member Adaptor.
Note: your Member Adaptor module may be called extend.py and be installed in a lists/<listname>/extend.py file for each list for which it applies or it may have some other name and be invoked globally in MailList.py in place of OldStyleMemberships()
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Jeffrey Borkent
-
Mark Sapiro