--- a/xml/dnsbl.in	Tue Jul 10 14:09:23 2007 -0700
+++ b/xml/dnsbl.in	Sat Jul 14 12:25:17 2007 -0700
@@ -176,11 +176,15 @@
                 allowed to relay thru this mail server with no spam filtering.
             </para>
             <para>
-                Consider the case of a message from A to B passing thru this milter.
-                If that message is not blocked, then we might eventually see a reply
+                Consider the case of a message from A to B passing thru this milter.  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 for a configurable time period.  Such autowhite
+                autowhite entry, and that context does <emphasis>not</emphasis> cover B
+                as a recipient, then this milter will add an entry in that file to
+                whitelist such replies for a configurable time period.  Suppose A and B
+                are in the same domain, or at least use the same filtering context.  In
+                that case we don't want to add a whitelist entry for B, since that would
+                then allow spammers to send mail from B (forged) to B. 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>