--- a/xml/dnsbl.in	Wed Apr 21 16:09:07 2004 -0700
+++ b/xml/dnsbl.in	Wed Apr 21 22:39:46 2004 -0700
@@ -18,9 +18,9 @@
 per-recipient basis, so that fred@example.com could use SPEWS and the
 SBL, where all other users @example.com use only the SBL.
 
-<p>The DNSBL milter reads a text configuration file on startup, and
-whenever the config file (or any of the referenced include files) is
-changed. The entire configuration file is case insensitive.
+<p>The DNSBL milter reads a text configuration file (dnsbl.conf) on
+startup, and whenever the config file (or any of the referenced include
+files) is changed.  The entire configuration file is case insensitive.
 
 <p>If you are also using the <a
 href="http://www.rhyolite.com/anti-spam/dcc/">DCC</a> milter, there are
@@ -48,7 +48,7 @@
 <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
+Presumably you can use rsync or scp to fetch copies of your 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
@@ -124,10 +124,19 @@
 
 Read the sample <a
 href="http://www.five-ten-sg.com/dnsbl.conf">var/dnsbl/dnsbl.conf</a>
-file and modify it to fit your configuration.
+file and modify it to fit your configuration.  You can test your
+configuration files, and see a readable internal dump of them on stderr
+with
+
+<pre>
+cd /var/dnsbl
+./dnsbl -c
+</pre>
+
+<pre>
 
 
-<pre>
+
 $Id$
 </pre>
 </body>