Re: [Assp-user] making trap addresses

[Donald B. <db...@fe...>]

I've looked and adjusted this a little, and observed it for a few days.
Trap addresses are still not scoring against the IP, they are just being
rejected
...
Mar-12-10 09:41:52 Connected: 95.59.68.69:2557 -> 192.168.0.205:25 ->
192.168.0.205:25255;
Mar-12-10 09:41:53 04913-14167 95.59.68.69 <gr...@nu...> rejected
by DoPenaltyMakeTraps: gr...@nu...



Don Brooks
db...@fe...
P
Pensons vert avant d'imprimer ce message!
Please think green before printing this message!
-----Original Message-----
From: Fritz Borgstedt [mailto:fb...@iw...] 
Sent: March-10-10 1:14 PM
To: For Users of ASSP
Subject: Re: [Assp-user] making trap addresses

My recommendation for ASSP V 1.7X is a little different.

ASSP caches unknown addresses (as before) but will use this cache to
validate the incoming addresses even if it is not a heavy used
address. If you set MaxErrors to 3  many connection will be
disconnected because of multiple unknown user . Greylisting will take
care of the rest. You end up with more than 90% of the connections not
reaching any stage where they suck resources.
Instead of using the heavy used addresses for trapaddresses, you may
use them as collect addresses, thereby getting a very solid
spam-collection.


------------------------------------------------------------------------
------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Assp-user mailing list
Ass...@li...
https://lists.sourceforge.net/lists/listinfo/assp-user