diff xml/dnsbl.in @ 160:b3ed72ee6564

allow manual updates to auto whitelist files
author carl
date Tue, 10 Jul 2007 11:20:23 -0700
parents ca4f178f9064
children d384df37491f
line wrap: on
line diff
--- a/xml/dnsbl.in	Sun Jul 08 11:57:51 2007 -0700
+++ b/xml/dnsbl.in	Tue Jul 10 11:20:23 2007 -0700
@@ -180,10 +180,9 @@
                 If that message is not blocked, then we might eventually see a reply
                 message from B to A. If the filtering context for A includes an
                 autowhite entry, then this milter will add an entry in that file to
-                whitelist such replies.  Note that manually editing such autowhite files
-                is not supported. Also, such autowhite files need to be writeable by the
-                dnsbl user, where all the other dnsbl configuration files only need
-                to be readable by the dnsbl user.
+                whitelist such replies for a configurable time period.  Such autowhite
+                files need to be writeable by the dnsbl user, where all the other dnsbl
+                configuration files only need to be readable by the dnsbl user.
             </para>
             <para>
                 The DNSBL milter reads a text configuration file (dnsbl.conf) on
@@ -264,11 +263,13 @@
             <para>
                 The SMTP envelope 'from' and 'to' values are used in various checks.
                 The first check is to see if a reply message (swapping the env_from and
-                env_to values) would be blocked.  That check is similar to the main
-                check described below, but there is no body content to be scanned, and
-                there is no client connection ip address to be checked against DNSBLs.
-                This prevents folks from sending mail to recipients that are unable to
-                reply.
+                env_to values) would be unconditionally blocked (just based on the
+                envelope from address).  That check is similar to the main check
+                described below, but there is no body content to be scanned, and there
+                is no client connection ip address to be checked against DNSBLs.  If
+                such a reply message would be blocked, we also block the original
+                outgoing message.  This prevents folks from sending mail to recipients
+                that are unable to reply.
             </para>
             <para>
                 If the client has authenticated with sendmail, the rate limits are
@@ -345,6 +346,12 @@
                 </para></listitem>
             </orderedlist>
             <para>
+                For each recipient that was accepted, we search for an autowhite entry
+                starting in the reply filtering context. If an autowhite entry is found,
+                we add the recipient to that auto whitelist file. This will prevent reply
+                messages from being blocked by the dnsbl or content filtering.
+            </para>
+            <para>
                 If content filtering is enabled for this body, the mail text is decoded
                 (uuencode, base64, mime, html entity, url encodings), and scanned for HTTP
                 and HTTPS URLs or bare host names.  Hostnames must be either ip address
@@ -493,7 +500,7 @@
             <para>
                 This program is free software; you can redistribute it and/or modify it
                 under the terms of the GNU General Public License as published by the
-                Free Software Foundation; either version 2, or (at your option) any
+                Free Software Foundation; either version 3, or (at your option) any
                 later version.
             </para>
             <para>