Milter-greylist

Emmanuel Dreyfus wrote:
> On Wed, Oct 12, 2005 at 11:55:31AM -0400, Matt Kettler wrote:
> 
>>4) using the lazyaw option will also greatly reduce the number of entries, at
>>the expense of making it much easier to get past the greylist.
> 
> 
> 5) buy some RAM :o)
> 
> Seriously, 2 GB seems really huge to me. I'd be curious to learn how many
> message per day flow through this machine. The problem may be caused by
> a memory leak (in milter-greylist or in a library)

We have just under 1 000 000 rows in the database.

The problems seem to begin with mxsyncing enabled. The amount of virtual
memory used seems to grow if milter-greylist is _recieveing_ mxsyncs. I 
have one of the servers configured to recieve syncs only and there is no 
milter-traffic to this server (and thus it generates no entries on its 
own). The instance of milter-greylist recieveing syncs allocates more 
and more VmData while the one actually doing the greylisting and sending 
the syncs does not.

Valgrind does not seem to find any leaks.

Please note that I am speaking of VmData, not resident memory. My system 
does not swap, so it seems that the memory is only reserved, and never used.

Any ideas?

Cheers,
Fredrik Nyberg