I've recently set up Mailman and Postfix to handle a couple of lists. I did hit one problem which I only managed to solve by a small amendment to the Mailman code. It would be nice to know if there's a better way!
The scenario is this. Mailman runs on the same server as the main MTA, running Postfix. There are *no* local users on this machine, apart from 'root', which is aliased elsewhere. In particular, the domain under which Mailman runs (let's call it xxx.org.uk) is a Postfix virtual domain, again with no local users. The machine's domain name is different (it handles mail for seven domains). When genaliases is run (either explicitly or otherwise) it generates a virtual aliases file of the form: [EMAIL PROTECTED] user1 [EMAIL PROTECTED] user2 etc. (this is in data/virtual-mailman). The problem is that the default domain for the RHS on this table is (in Postfix terms) $mydomain, which is *not* xxx.org.uk; it's another virtual domain. Thus there is no local delivery, and the local alias file is never invoked to call up the Mailman components. What this situation needs is for the table entries to look like: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] so that the local aliases file gets used. I fixed this by modifying the POSTFIX module to use an optional email host setting, then put a default (null) for that in Defaults.py, and a setting value in mm_cfg.py. Is there a better way that I've missed? Bob ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org 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
