Steve Tornio wrote: > On Sep 27, 2006, at 6:10 PM, Rickard Borgmdster wrote: > >> >> What I see as the problem here, is that the "blacklisting" occurs before >> the whitelisting. So that, when a large block such as 31.32.33.0/24 is >> in <spamd> and I wish to whitelist 31.32.33.188, that whitelist entry >> will have no effect. > > This is solved in spamd, not pf. Have a look at spamd.conf (5) In > short, you specify whitelists to be applied in conjunction with certain > blacklists.
So that if 31.32.33.0/24 is blacklisted, and I put a whitelist entry of 31.32.33.188 in whitelist.txt, will spamd "break" the /24 into segements which are individually blocked like this? 31.32.33.0/25 31.32.33.128/27 31.32.33.160/28 31.32.33.176/29 (176-183) 31.32.33.176/30 (184-187) 31.32.33.176.189 31.32.33.176 31.32.33.176.190 31.32.33.176.191 31.32.33.192/26 If that is the case, it's terrific :-) But it still doesn't take care of the "fastlane", so that whitelisted host doesn't have to go trough the greylist process. Or does it? Best regards Rickard Borgmdster
