An alternative way to eliminate the handling of aliases is to move to Postfix and use the Mailman/Postfix integration. Now that is a win-win situation.
You can actually mimic this integration with Sendmail if you use a cron script (or modify the new-list app to include the script commands), to run genaliases and pump the output to a local file which you then hash via newaliases: ~mailman/data/aliases ~malman/data/aliases.db After that you simply edit /etc/sendmail.cf to look at both alias files: /etc/aliases, and ~mailman/data/aliases Hope this helps someone - Jon Carnes (reformed Sendmail junkie) === On Thu, 2003-01-30 at 05:03, Richard Barrett wrote: > At 21:51 29/01/2003, Jon Carnes wrote: > >If you can get shell access to the server you can use the > >~mailman/bin/genaliases command to generate the aliases for your created > >lists. You could simply redirect the output of that command into a > >local aliases file and then include that aliases file in your MTA's list > >of aliases that it checks. > > > >Jon Carnes > > > > If the MTA is sendmail then there is an option of using a sendmail mailer > to deliver to Mailman, if the only mail aliases on the server are the small > number of standard local aliases, e.g. postmaster, and those for Mailman > lists. If the machine is also hosting aliases for individual users then > forget I posted this. > > MM 2.1 has the mm-handler contrib which is a sendmail mailer implemented in > Perl. There is also a Python implementation available which I have posted > as MM patch #644810 on sourceforge. Note that the Perl contrib isn't > entirely bullet-proof, unless the author has recently fixed an issue I > raised a while back. > > Using these sendmail mailers can completely eliminate maintenance of mail > aliases on a list server. Create the list with MM through the web GUI and > its ready to go. The downside is some hassle getting sendmail setup right > and I wouldn't rate this as a job for a sendmail novice unless he is a > persistent one like me. But once that is done, no alias maintenance hassle. > > I started out using the Perl contrib (originally with my own modifications > to work with MM 2.0.13 rather than 2.1) but now use the Python version on a > dedicated list server machine and its backup, which are currently hosting > over 450 fairly lightly loaded lists. The list population is fairly dynamic > and the use of the sendmail mailer works well for me. > > >On Wed, 2003-01-29 at 06:24, Will Nordmeyer wrote: > > > Hi, > > > > > > I'm using mailman 2.1 on a Cobalt RAQ3 and trying to use the web > > > interface to create a list. > > > > > > It creates the list, but doesn't add any entries to either the aliases > > > file or the virtusertable. It also doesn't provide a list of what > > > entries need to be added. > > > > > > It doesn't seem that I have everything configured right but don't see > > > anything in the INSTALL doc about the settings. > > > > > > Can someone help please? > > ------------------------------------------------------ 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
