At 5:55 PM +0000 2005-03-08, Matthew Newton wrote:
If there is no standard way of doing this, I will probably look at writing a patch where there is a list, say mm_cfg.RESTRICT_CHANGES, that contains all configuration sections that should not be shown. Is this a good idea?
That sounds like a reasonable solution.
I would also like to hook into the subscription code to, do at least two things: automatically change all addresses with s/@le\.ac\.uk$/@leicester.ac.uk/ and to block subscription requests that match /@lists\.le(icester)?\.ac\.uk/ (I do not want to allow umbrella lists). Is there a standard way, or hook into the code, for doing this (on a site-wide basis, not per list)?
I'm not aware of a standard way to do this sort of stuff.
-- Brad Knowles, <[EMAIL PROTECTED]>
"Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755SAGE member since 1995. See <http://www.sage.org/> for more info. ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
