>> This leads me to ask for another modification - can you add links
>> from
>> each of the test enable dropdowns (disabled/block/monitor/score) to
>> the
>> appropriate PB scoring value and the reverse?  I think it will really
>> make adjusting these values easier - especially for newcomers to
ASSP.

> That is a lot of work.

Agreeed, and I'm not sure it may be really needed, let me add my 2 cents

We all know there are two kinds of DNSBLs; the "aggressive" ones and
the "conservative" ones; now, the request makes sense if you want to
use aggressive lists together with conservative ones, but assigning a
lower score to the first and an higher one to the seconds; but to do
that,
imVHo there's no need to setup such a complex system

The current ASSP options allow you to specify how many DNSBL "hits"
ASSP will need to consider a message spam/ham; such an approach
may seem ok, but has some slight problems

let's say you mix aggressive and conservative lists, then you setup the
hits count to 2

an incoming mail hits (say) "dnsbl-2.uceprotect.net" which is an
"aggressive"
list, so you don't want to block only for that hit; but only if another
list tells you
that the IP is a "bad one"; so if there isn't another hit, the mail gets
through;

till now, all ok, but ...

an incoming mail hits (say) "zen.spamhaus.org"  and since it's a
conservative
list you want to BLOCK the incoming mail, but since there's no hit from
other
lists, the message goes through

and this is a problem, since there's currently no way to tell ASSP if a
given
list is an "aggressive" or "conservative" one and the "hits" approach
doesn't
help here, so we may need something else

Let's say ASSP exposes TWO entries for DNSBLs; a "conservative" one
(the current one) and a new "aggressive" one containing the lists which
will
only be used for "scoring"; upon startup ASSP will load both lists and
will
use both as if they were a single one ... but with a tweak; hits
received from
the second (aggressive) won't block, they'll just increase the "spam
score"
of the incoming email (but won't increase the hits count which will only
be
used/increased by the "conservative" list); this will allow to use both
types
of lists withouth too many risks and avoiding the problem shown above

from a "coding" point of view; the above means that ASSP will load two
files (conservative/aggressive) but will just create a single DNSBL
"array"
containing a "type" and a "name"; the type will tell ASSP how to handle
the
answers from a given list (i.e. increase-hits for the "conservative"
ones or
increase-spamscore for the aggressive ones)

maybe it could be easier and worth implementing ?



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to