Norman Maurer wrote:
<handler
class="org.apache.james.smtpserver.core.filter.fastfail.DNSRBLHandler"
onCommand="RCPT">
<action> junkScore </action>
<match> +10 </match>
<notmatch> 0 </notmatch>
</handler>
Imho match/nomatch is not so good... imho it is always better to use a
single match and put there the "match - nomatch" result.
You're simply moving the offset.. so you'd better check for a
different result at the end.
Simplicity is the key ;-)
Well with <match> and <notmatch> the admin could do more flexible
configs... It was just a idea..
Can you make an example of what you can do with match/nomatch that
cannot be done using only match? (maybe I missed something but I cannot
thing at one scenario where it happens)
Meta-Example:
---------
<handler1><match>+10</match><nomatch>-5</nomatch></handler1>
<handler2><nomatch>-7</nomatch></handler2>
<handler3><match>+4</match></handler3>
<junkHandler>if junkscore > 5: reject</junkHandler>
---------
Is the same of
---------
<handler1><match>+15</match></handler1>
<handler2><match>+7</match></handler2>
<handler3><match>+4</match></handler3>
<junkHandler>if junkscore > 17: reject</junkHandler>
---------
Isn't this simpler?
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
