Milter-greylist

On Mon, Sep 11, 2006 at 10:00:00AM +0300, Mart Pirita wrote:
> acl greylist default delay 15m code "451" ecode "4.7.1" msg "greylisted"
> timeout 3h
> autowhite 0
> 
> Still some passes true. Now maybe I should set the delay 30m and timeout 30m?

Some spamware handle resending now. They seems to give up against a delay
of several hours. 

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.

> And if is set autowhite 0 then why is this "autowhitelisted for 00:00:00" shown in
> logs at all:

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.

> And why one minute later autowhitelisted entry expired, not in the same moment
> when autowhitelisted for 00:00:00?

Because we never specifically hunt for timeouts in the database. The 
functions that have to walk the database for some reason take care of
removing expired entries. If you have no incoming mail, the expired entries
are not flushed, but that does not really matter, since they are not used.

-- 
Emmanuel Dreyfus
manu@...