Further to what I said on 2nd Aug, I have now adapted the 2.1b2 contrib 
mm-handler to work with MM 2.0.x and I'm now using it instead of an aliases 
file in conjunction with Sendmail on our mailing list server. Works OK and 
will put me in better shape for the switchover to MM 2.1.

In addition to changes in the Perl mailer I also had to make some changes 
in the m4 macros used to generate the sendmail.cf to get the mailertable to 
work as planned. This may just be an artifact of the sendmail m4 files 
installed by Suse 7.3 that I'm running on the machine. Or it could be due 
to my limited knowledge of Sendmail and its configuration and hence be a 
stupid change.

If, having looked at the 2.1b2 contrib mm-handler and in particular perused 
the readme for it, anybody is interested in a copy of the Perl mailer code 
changes I made so that it will work with 2.0.x or the Sendmail m4 macro 
hacks then just ask. Its definitely not rocket science and comes with no 
warranty but it might save you some time.

-------on 2nd Aug 2002 I originally said:

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/

Reply via email to