Re: [Assp-user] Upcoming Release & Starter Configuration

[Marrco <as...@mi...>]

>>so my suggestion is to start easy and default assp to use a single
>>list (of
>>known good hosts) for all 'ip pass' strategies.
>
> I have too see besides your view what the bayesian filter needs. And
> so there is a fundamental difference between a nonprocessing and
> whitelisted list.

of course you do. Your server, your rules. Different strategies, same goal. 
Assp is great also because it suits everyone needs, not only mine.

anyway, imho we have 3 different whitelist categories :

-) huge world wide mailhubs (gmail, hotmail, etc) - IPs are 100% good, never 
block them. Many are already listed in nodelay.txt
-) my ( i'm italian) very important italian mail providers - IPs are 100% 
good, never block them, and never refuse any mail but viruses and a few 
exceptions
-) your well know german (dutch, chinese, australian etc) local providers. 
Ok, i trust you they are not trojaned computers, so maybe i wont use 
delaying but no other favours on my servers.

so i think all we need is an expanded nodelay.txt that includes a few more 
large mailhubs. And use that also to bypass ip filtering (rbl, validate 
sender, PB, griplist etc)

plus any postmaster should whitelist his own 'special' local mail hubs. 
That's easy. A small script to extract the top connectiong hosts to your 
mta, sort them, have a reverse lookup and then you easily decide what ips 
you have to whitelist.