Milter-greylist

I decreased the timeout from 5 days to 26 hours for keeping tuples.  My
database decreased to 400 KB.

What's the point in keeping tuples for so long?

If my greylist_delay is 6 minutes, I would think we could discard tuples
after 10 minutes, assuming that timeout does not affect the time for
auto-white-listing.

Jim

________________________________

	From: milter-greylist@yahoogroups.com
[mailto:milter-greylist@yahoogroups.com] On Behalf Of manu@...
	Sent: Friday, August 25, 2006 12:20 AM
	To: milter-greylist@yahoogroups.com
	Subject: Re: [milter-greylist] milter-greylist 2.02 crashes
	
	
	
	Jim Hermann - UUN Hostmaster <hostmaster@...
<mailto:hostmaster%40uuism.net> > wrote:
	
	> I don't have gdb available, so I have been running in foreground
with the
	> -Dv options. The only crash so far left a message about an Alarm. 
	> 
	> Also, it appears that milter-greylist may be more stable in
verbose mode. I
	> ran the Daemon for a couple of days in verbose mode without any
incidents.
	
	That suggests a timing-dependent issue, since the olny difference is
	that it gets slower due to debug printf.
	
	> One thing that I have noticed is that my greylist.db is over 3 MB.
	> 
	> Why does milter-greylist keep tuples that were delayed and did not
retry
	> before the greylist_delay transpired?
	
	When we cleanup any tuple, we have to walk the database, and we use
that
	opportunity to cleanup any expired entry we find.