Sounds like maintaining centralized administration is going to be to hard. With Mailman 2.1 you have the power to give away the administration of various lists to other users (or administrative assistants).
Each School and Institute must have some worthy admin or assistant that works there and is knowledgeable about the personnel. And since you don't have to be a genius to maintain the users lists via the web, it should be easy for that individual to maintain the lists specific to that venue. You might want to setup a policy stating that no mailing lists will be created/setup without an appropriate administrator being assigned first. That administrator is responsible for overseeing the membership of the list and formalizing any requested changes to its format. Part of the design of Mailman 2.1 is to allow you to share the burden. Good Luck - Jon Carnes On Mon, 2003-09-22 at 14:09, Steve Sweet wrote: > We've been using mailman for several months now, and both we (the > administrators) and they (the users) have been happy with it. So much so in > fact, that we have now been asked to create so many different lists its become > an administrative nightmare. I'm hoping someone more experienced will have > suggestions on how to tame the monster we've created. > > We're running mailing lists for one school within a university. The school has > several hundred subscribers (personnel) split amongst faculty, staff and > students, a number of different institutes and programs, all spread over 6 > different geographic locations. There are members of each institute at each > location. There are members of each program at each location, and within each > institute. Each location, institute and program has faculty, staff, and students. > > We have been asked to create a list for essentially every different permutation; > all faculty, all faculty at location A, all faculty at location A in program B, > all faculty at location A in institute B and program C, all staff ... you get > the point. > > This is an enormous mess of lists and keeping up with them is tedious and time > consuming. Relying on the users to adminster themselves helps somewhat -- the > students are generally good at it -- but the staff are not and the faculty are > hopeless. The administration has been clear that we need to make sure the list > memberships are kept up to date since vital notices go out via the lists. > > Any suggestions before I pull whats left of my hair out? > > ------------------------------------------------- > This mail sent through IMP: http://horde.org/imp/ > > ------------------------------------------------------ > 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/ > > This message was sent to: [EMAIL PROTECTED] > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com ------------------------------------------------------ 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
