[Mailman-Developers] Latest tweaks to README.EXIM
Greg Ward
gward@python.net
Wed, 16 Oct 2002 10:03:09 -0400
Barry -- Nigel M. suggested a couple of tweaks to README.EXIM on
exim-users; here's the patch. Not tested yet.
--- README.EXIM 15 Oct 2002 22:14:16 -0000 2.5
+++ README.EXIM 16 Oct 2002 14:01:23 -0000
@@ -26,10 +26,10 @@
The drawback of this configuration is that it will work poorly on
systems supporting lists in several different mail domains. While
Mailman handles virtual domains, it does not yet support having two
-lists with the same name in different virtual domains, using the same
-Mailman installation. This will eventually change. (But see below for
-a variation on this scheme that should accommodate virtual domains
-better.)
+distinct lists with the same name in different virtual domains, using
+the same Mailman installation. This will eventually change. (But see
+below for a variation on this scheme that should accommodate virtual
+domains better.)
The configuration file excerpts below are for use in an already
functional Exim configuration, which accepts mail for the domain in
@@ -38,10 +38,10 @@
* add the list domain, "my.list.domain" to local_domains
- * add a "domains=my.list.domain" option to each of the directors
- (routers) for the list
+ * add a "domains=my.list.domain" option to the director
+ (router) for the list
- * (optional) exclude that domain from the other directors (routers)
+ * (optional) exclude that domain from your other directors (routers)
[Note: the instructions in this document should work with either Exim 3
or Exim 4. In Exim 3, you must have a 'local_domains' configuration
@@ -53,8 +53,8 @@
Whether you are using Exim 3 or Exim 4, you will need to add some macros
to the main section of your Exim config file. You will also need to
-define one new transport. With Exim 3, you'll need to add two new
-directors; with Exim 4, two new routers play the same role.
+define one new transport. With Exim 3, you'll need to add a new
+director; with Exim 4, a new router plays the same role.
Finally, the configuration supplied here should allow co-habiting
Mailman 2.0 and 2.1 installations, with the proviso that you'll probably
@@ -66,7 +66,7 @@
~~~~~~~~~~~~~~~~~~~~~~~~~~~
First, you need to add some macros to the top of your Exim config file.
-These just make the directors (routers) and transport below a bit
+These just make the director (router) and transport below a bit
cleaner. Obviously, you'll need to edit these based on how you
configured and installed Mailman.
@@ -103,53 +103,41 @@
please let me know if it works?)
-Directors for Exim 3
-~~~~~~~~~~~~~~~~~~~~
+Director for Exim 3
+~~~~~~~~~~~~~~~~~~~
-If you're using Exim 3, you'll need to add the following two directors
-to your config file (directors go between the second and third "end"
+If you're using Exim 3, you'll need to add the following director to
+your config file (directors go between the second and third "end"
lines). Also, don't forget that order matters -- e.g. you can make
-Mailman lists take precedence over system aliases by putting these
-directors in front of your aliasfile director, or vice-versa.
-
- # Director to handle a list's main posting address. Should come first
- # in case there's a list named, e.g. "mailman-owner". Automatically
- # detects list existence by looking for lists/$local_part/config.pck
- # under MAILMAN_HOME.
- mailman_main_director:
- driver = smartuser
- require_files = MAILMAN_HOME/lists/$local_part/config.pck
- transport = mailman_transport
+Mailman lists take precedence over system aliases by putting this
+director in front of your aliasfile director, or vice-versa.
- # Handle all the other addresses related to a list: -bounces, -admin,
- # etc. Same trick works to detect list existence thanks to the
- # 'suffix' option.
+ # Handle all addresses related to a list 'foo': the posting address.
+ # Automatically detects list existence by looking
+ # for lists/$local_part/config.pck under MAILMAN_HOME.
mailman_director:
driver = smartuser
require_files = MAILMAN_HOME/lists/$local_part/config.pck
+ suffix_optional
suffix = -bounces : -bounces+* : \
-confirm+* : -join : -leave : \
-owner : -request : -admin
transport = mailman_transport
-Routers for Exim 4
-~~~~~~~~~~~~~~~~~~
+Router for Exim 4
+~~~~~~~~~~~~~~~~~
-In Exim 4, there's no such thing as directors -- you instead need to add
-two routers. Also, the canonical order of the configuration file was
-changed so routers come before transports, so the routers for Exim 4
-come first here. Put these two routers somewhere after the "begin
-routers" line of your config file, and remember that order matters.
-
- mailman_main_router:
- driver = accept
- require_files = MAILMAN_HOME/lists/$local_part/config.pck
- transport = mailman_transport
+In Exim 4, there's no such thing as directors -- you need to add a new
+router instead. Also, the canonical order of the configuration file was
+changed so routers come before transports, so the router for Exim 4
+comes first here. Put this router somewhere after the "begin routers"
+line of your config file, and remember that order matters.
mailman_router:
driver = accept
require_files = MAILMAN_HOME/lists/$local_part/config.pck
+ local_part_suffix_optional
local_part_suffix = -bounces : -bounces+* : \
-confirm+* : -join : -leave : \
-owner : -request : -admin
@@ -306,8 +294,7 @@
VERP_DELIVERY_INTERVAL = 1
VERP_CONFIRMATIONS = 1
-(The directors/routers above are smart enough to deal with VERP
-bounces.)
+(The director (router) above is smart enough to deal with VERP bounces.)
Virtual Domains
@@ -319,7 +306,7 @@
the same machine.)
In this case, the MAILMAN_HOME and MAILMAN_WRAP macros are useless --
-you can remove them. Change your directors (routers) to something like
+you can remove them. Change your director (router) to something like
this:
require_files = /virtual/${domain}/mailman/lists/${lc:$local_part}/config.pck
--
Greg Ward <gward@python.net> http://www.gerg.ca/
And now for something completely different.