I use the Exim configuration documented on the Exim website at http://www.exim.org/howto/mailman21.html
It seems to work well and I think it looks cleaner than your suggestion. I thought it looked more up to date and superior version supplied by Mailman upstream. I use a GID of "daemon" as that is what the README.EXIM.gz file supplied with Debian Mailman has always instructed. I don't understand why you're using MTA = "Postfix", as it seems to make things more complicated and all the documentation says to use MTA=None with Exim. (Is it so that the Mailman domains can be set in mm_cfg.py instead of in the Exim config?) Could these files be installed automatically by the Mailman package, as suggested by Tollef in http://lists.debian.org/debian-devel/2005/02/msg00965.html ? I assume that mm_domains could be made to default to the contents of /etc/mailname. For most users I imagine that it might be possible to remove mm_domains altogether, and replace it with local_domains. Better would be if it could be set from something like /etc/exim4/update-exim4.conf.conf, but I don't suppose that would be possible without a nasty hack? The priority of each file is worked out from the description in the Exim howto. Hope this helps, Roger /etc/exim4/conf.d/main/10_local_mailman: # Home dir for your Mailman installation -- aka Mailman's prefix # directory. # By default this is set to "/usr/local/mailman" # On a Red Hat/Fedora system using the RPM use "/var/mailman" # On Debian using the deb package use "/var/lib/mailman" # This is normally the same as ~mailman MM_HOME=/var/lib/mailman # # User and group for Mailman, should match your --with-mail-gid # switch to Mailman's configure script. # Value is normally "mailman" MM_UID=list MM_GID=daemon # # Domains that your lists are in - colon separated list # you may wish to add these into local_domains as well domainlist mm_domains=list.example.com # # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # # These values are derived from the ones above and should not need # editing unless you have munged your mailman installation # # The path of the Mailman mail wrapper script MM_WRAP=MM_HOME/mail/mailman # # The path of the list config file (used as a required file when # verifying list addresses) MM_LISTCHK=MM_HOME/lists/${lc::$local_part}/config.pck /etc/exim4/conf.d/router/450_local_mailman: mailman_router: driver = accept domains = +mm_domains require_files = MM_LISTCHK local_part_suffix_optional local_part_suffix = -admin : \ -bounces : -bounces+* : \ -confirm : -confirm+* : \ -join : -leave : \ -owner : -request : \ -subscribe : -unsubscribe transport = mailman_transport /etc/exim4/conf.d/transport/30_local_mailman: mailman_transport: driver = pipe command = MM_WRAP \ '${if def:local_part_suffix \ {${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} \ {post}}' \ $local_part current_directory = MM_HOME home_directory = MM_HOME user = MM_UID group = MM_GID -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
