Milter-greylist

Tere.
>
> Some spamware handle resending now. They seems to give up against a delay
> of several hours. 
>   
I hope so, but I can't set 4h delay as legal senders and receivers are
going mad.
> Of course several hours is not something you want for any sender, this is
> where using dynamic pool DNSRBL helps: I use several hours for cable and
> DSL pools, qnd 15 mn for other hosts.
>   
Idea is good but I almost cant use it, as like I said, also at least 70%
legal senders are using dynamic ip -s and this blocks them also and it's
no good. Maybe I should use some other (which?) DNSRBL server to let
pass the good ones (near countries) and block the bad (asia etc)?
>
> The 0 minutes dalay for autowhitelisting implementation is subotptimal for 
> now, as an entry is still created in the database. The semantics is right, 
> through: there is no autowhitelisting, as the autowhitelisting entry is
> already expired when it is inserted in the database.
>
> In a future release I'll take care of not creating an entry at all.
>   
Ok.
> Because we never specifically hunt for timeouts in the database. The
> functions that have to walk the database for some reason take care
> ofremoving expired entries. If you have no incoming mail, the expired
> entriesare not flushed, but that does not really matter, since they
> are not used.
>
Ok.

-- 
Mart