--- a/xml/dnsbl.in	Wed Apr 21 12:52:29 2004 -0700
+++ b/xml/dnsbl.in	Wed Apr 21 16:09:07 2004 -0700
@@ -28,11 +28,7 @@
 bulk detector, or from the DNS based lists.  Those are two very
 different reasons for whitelisting.  The former is done thru the DCC
 whiteclnt config file, the later is done thru the DNSBL milter config
-file.  There is an option to reference the DCC whiteclnt file (via an
-include_dcc line) in the DNSBL milter config.  This will import the
-(env_to, env_from, and substitute mail_host) entries from the DCC config
-into the DNSBL config.  This allows using the DCC config as the single
-point for white/blacklisting.
+file.
 
 <p>You may want to blacklist some specific senders or sending domains.
 This could be done thru either the DCC (on a global basis, or for a
@@ -43,6 +39,23 @@
 feature that the mail is rejected earlier (at RCPT TO time), and the
 sending machine just gets a generic "550 5.7.1 no such user" message.
 
+<p>There is an option to reference the DCC whiteclnt file (via an
+include_dcc line) in the DNSBL milter config.  This will import the
+(env_to, env_from, and substitute mail_host) entries from the DCC config
+into the DNSBL config.  This allows using the DCC config as the single
+point for white/blacklisting.
+
+<p>Consider the case where you have multiple clients, each with their
+own mail servers, and each running their own DCC milters.  Each client
+is using the DCC facilities for envelope from/to white/blacklisting.
+Presumably you can use rsync or scp to fetch copies of these clients DCC
+whiteclnt files on a regular basis.  Your mail server, acting as a
+backup MX for your clients, can use the DNSBL milter, and include those
+client DCC config files.  The envelope to white/blacklisting will be
+global for your system, but the envelope from white/blacklisting will be
+appropriately tagged and used only for the domains controlled by each of
+those clients.
+
 <p>Definitions:
 
 <p>DNSBL - a named DNS based blocking list is defined by a dns suffix