diff xml/dnsbl.in @ 203:92a5c866bdfa

Verify from/to pairs even if they might be explicitly whitelisted. Document DCC greylisting and bulk detection usage. Fix DCC bulk thresholds of many. Update spec file for fedora packaging.
author Carl Byington <carl@five-ten-sg.com>
date Tue, 04 Mar 2008 21:42:51 -0800
parents 752d4315675c
children 82886d4dd71f
line wrap: on
line diff
--- a/xml/dnsbl.in	Sat Feb 02 12:32:59 2008 -0800
+++ b/xml/dnsbl.in	Tue Mar 04 21:42:51 2008 -0800
@@ -423,7 +423,21 @@
                 If any non-whitelisted recipient has a filtering context with a non-zero
                 spamassassin limit, then the message is passed thru spamassassin (via
                 spamc), and the message is rejected for those recipients with spamassassin
-                limits less than the resulting spamassassin score.
+                limits less than the resulting spamassassin score. For example, a
+                spamassassin limit of three will reject messages with spamassassin scores
+                of four or greater.
+            </para>
+            <para>
+                If any non-whitelisted recipient has a filtering context that specifies
+                DCC greylisting, then the message is passed thru the DCC bulk detector,
+                and the message is greylisted (for all recipients) if the DCC says this
+                message should be delayed.
+            </para>
+            <para>
+                If any non-whitelisted recipient has a filtering context with a non-zero
+                DCC bulk threshold, then the message is passed thru the DCC bulk detector,
+                and the message is rejected for those recipients with DCC thresholds less
+                than or equal to the DCC bulk score.
             </para>
             <para>
                 We also scan for excessive bad html tags, and if a &lt;configurable&gt;