--- a/xml/dnsbl.in	Thu Oct 04 22:45:21 2007 -0700
+++ b/xml/dnsbl.in	Sat Oct 06 10:56:35 2007 -0700
@@ -34,6 +34,7 @@
                 <arg><option>-s</option></arg>
                 <arg><option>-d <replaceable class="parameter">n</replaceable></option></arg>
                 <arg><option>-e <replaceable class="parameter">from|to</replaceable></option></arg>
+                <arg><option>-b <replaceable class="parameter">local-domain-socket</replaceable></option></arg>
                 <arg><option>-r <replaceable class="parameter">local-domain-socket</replaceable></option></arg>
                 <arg><option>-p <replaceable class="parameter">sendmail-socket</replaceable></option></arg>
                 <arg><option>-t <replaceable class="parameter">timeout</replaceable></option></arg>
@@ -72,7 +73,14 @@
                     </para></listitem>
                 </varlistentry>
                 <varlistentry>
-                    <term>-r <replaceable class="parameter">local-domain-socket</replaceable></term>
+                    <term>-b <replaceable class="parameter">local-domain-socket-file-name</replaceable></term>
+                    <listitem><para>
+                        Set the local socket used for the connection to the dccifd daemon.
+                        This is typically /var/dcc/dccifd.
+                    </para></listitem>
+                </varlistentry>
+                <varlistentry>
+                    <term>-r <replaceable class="parameter">local-domain-socket-file-name</replaceable></term>
                     <listitem><para>
                         Set the local socket used for the connection to our own dns resolver processes.
                     </para></listitem>
@@ -248,6 +256,18 @@
                 be appropriately tagged and used only for the domains controlled by each
                 of those clients.
             </para>
+            <para>
+                You can now use (via dccifd) different dcc filtering parameters on a per
+                context basis.  See the dcc_greylist and dcc_bulk_threshold statements
+                in the <citerefentry> <refentrytitle>@PACKAGE@.conf</refentrytitle>
+                <manvolnum>5</manvolnum> </citerefentry> configuration.  Those
+                statements are only active if you supply the <option>-b</option> option
+                on the dnsbl command line.  If you use the dcc via the standard dcc
+                milter (dccm), then connections from clients that use SMTP AUTH are
+                still subject to greylisting.  If you use the dcc via dccifd and this
+                milter, then connections from clients that use SMTP AUTH are never
+                subject to greylisting.
+            </para>
         </refsect1>
 
         <refsect1 id='definitions.1'>
@@ -704,6 +724,7 @@
     env_to {
         # !! replace this with your domain names
         # child contexts are not allowed to specify recipient addresses outside these domains
+        # if this is a backup-mx, you need to include here domains for which you relay to the primary mx
         include "/etc/mail/local-host-names";
     };