As a possible alternative, there is a contribution in the contrib folder of the MM 2.1b2 release ($build/contrib/mm-handler) whose use obviates extending Sendmail's aliases database every time a new Mailman list is added or an old one removed.
It is a Sendmail Mailer (its a Perl script) which calls the Mailman programs to handoff mail from Sendmail to Mailman. It is "driven" Mailman's list "database". Hence it dynamically starts delivery to new lists and stops delivery to removed lists without any need to maintain a separate Sendmail aliases database. I cannot see any reason why this should work just as well with MM 2.0.x as with MM 2.1.x; indeed I'm going to switch over to using it on my production MM 2.0.13 installation if I can first install it successfully on my test 2.1b2 installation. At 15:39 01/08/2002 -0700, Gary Verhulp wrote: >newlist -o /etc/aliases : newaliases > >I think this is what you are asking for > >Gary > > >Larry Guest wrote: > >>Is there a better way to handle the mailman aliases instead of just editing >>my /etc/aliases file and running newaliases. >>When I get to over 200 lists its going to be a nightmare file. >> >>Thanks >> ------------------------------------------------------ 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/
