On Fri, Jul 18, 2008 at 6:09 PM, Constantine A. Murenin <mureninc@...> wrote: > * My current understanding, not explicitly supported by > greylist.conf(5), is that with milter-greylist this 'timeout' value > corresponds to the period of time that the greylisting tuples are > stored after the greylist time is already over, e.g. if you have > 'greylist 1h' and 'timeout 4h', then the total time the brute force > tuples are stored before being ejected is 5h, not 4 hours as it would > have been with the suggested timeout terminology from the original > whitepaper and some other greylisting implementations. That can't be right but I vaguely remember that the actual cleansing of the database is done not directly at timeout but following some other algorithm, probably when there's a number of tuples to remove. Maybe that's why you think it's the sum of those times or because the actual database is in memory, the disk copy is just that - a copy dumped periodically so that file can contain tuples no longer in memory. /peter -- Laurence J. Peter - "Originality is the fine art of remembering what you hear but forgetting where you heard it."
Message
Re: [milter-greylist] size of /var/milter-greylist/greylist.db
2008-07-18 by shuttlebox
Attachments
- No local attachments were found for this message.