From 7fd3afbe2480275fe41fa0169ed72abd1f425048 Mon Sep 17 00:00:00 2001 From: bwarsaw <> Date: Tue, 14 Dec 2004 04:27:49 +0000 Subject: Committing lots of documentation updates, including linking up to the new mailman-installation guide, and filling out the other formats that seemed to be missing. --- admin/www/mailman-install/node25.html | 134 ++++++++++++++++++++++++++++++++++ 1 file changed, 134 insertions(+) create mode 100644 admin/www/mailman-install/node25.html (limited to 'admin/www/mailman-install/node25.html') diff --git a/admin/www/mailman-install/node25.html b/admin/www/mailman-install/node25.html new file mode 100644 index 00000000..ad16c524 --- /dev/null +++ b/admin/www/mailman-install/node25.html @@ -0,0 +1,134 @@ + + +
+ + + + + + + + + ++Exim's receiver verification feature is very useful - it lets Exim reject +unrouteable addresses at SMTP time. However, this is most useful for +externally-originating mail that is addressed to mail in one of your local +domains. For Mailman list traffic, mail originates on your server, and is +addressed to random external domains that are not under your control. +Furthermore, each message is addressed to many recipients +- up to 500 if you use Mailman's default configuration and don't tweak +SMTP_MAX_RCPTS. + +
+Doing receiver verification on Mailman list traffic is a recipe for trouble. +In particular, Exim will attempt to route every recipient addresses in +outgoing Mailman list posts. Even though this requires nothing more than a +few DNS lookups for each address, it can still introduce significant delays. +Therefore, you should disable recipient verification for Mailman traffic. + +
+Under Exim 3, put this in your main configuration section: + +
+
+ receiver_verify_hosts = !127.0.0.1 +
+Under Exim 4, this is probably already taken care of for you by the default
+recipient verification ACL statement (in the RCPT TO
ACL):
+
+
+
+ accept domains = +local_domains + endpass + message = unknown user + verify = recipient +
+which only does recipient verification on addresses in your domain. (That's +not exactly the same as doing recipient verification only on messages coming +from non-127.0.0.1 hosts, but it should do the trick for Mailman.) + +
+ +
+ + + + -- cgit v1.2.3