dnsbl: xml/dnsbl.in comparison

actually use spamassassin result, allow build without spam assassin, only call it if some recipient needs it.

comparison

equal deleted inserted replaced

-:7161d8451fcf
+:9b129ed78d7d
 </partintro>
 <refentry id="@PACKAGE@.1">
 <refentryinfo>
-<date>2007-07-26</date>
+<date>2007-07-27</date>
 </refentryinfo>
 <refmeta>
 <refentrytitle>@PACKAGE@</refentrytitle>
 <manvolnum>1</manvolnum>
 If the content uribl DNSBL is defined, and any of those host names are
 on that DNSBL, and the host name is not on the &lt;configurable&gt;
 ignore list, the mail is rejected.
 </para>
 <para>
-If the spamassassin limit for this filtering context is non-zero, the
+If any non-whitelisted recipient has a filtering context with a non-zero
-message is passed thru spamassassin (via spamc) and if the resulting
+spamassassin limit, then the message is passed thru spamassassin (via
-score is larger than this limit, the mail is rejected.
+spamc), and the message is rejected for those recipients with spamassassin
+limits less than the resulting spamassassin score.
 </para>
 <para>
 We also scan for excessive bad html tags, and if a &lt;configurable&gt;
 limit is exceeded, the mail is rejected.
 </para>
 </refentry>
 <refentry id="@PACKAGE@.conf.5">
 <refentryinfo>
-<date>2007-07-26</date>
+<date>2007-07-27</date>
 </refentryinfo>
 <refmeta>
 <refentrytitle>@PACKAGE@.conf</refentrytitle>
 <manvolnum>5</manvolnum>

Mercurial > dnsbl