Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

dumpfreq and greylist timeout

2008-03-19 by Eduardo Casarero

Hi, i'd like to comment some experiences we detected today with milter-greylist in dumping db activities.

In big systems (we have more than 10 servers that handles 80k of emails and rejects 300k of connections) we notice that the dump needs lots of resources, but that is not the only issue the problem is that during the dump process all sendmail traffic get queued in the box without greylisting, we see in the log lots of this message.

Mar 19 09:12:49 XXXXXXX sm-mta[765]: m2JECaMo000765: Milter (greylist): timeout before data read
Mar 19 09:12:49 XXXXXXX sm-mta[765]: m2JECaMo000765: Milter (greylist): to error state

So a lot of traffic gets queued generating a quick grow of our inbound mqueue.

We solved this increasing dumpfreq to 1 day so in case of crash we dont lose too much, also we enable dump_no_time_translation to do a fastest dump.

Note: our greylist.db size is aprox 250 Mb (milter-greylist v 4.0)

Is this a normal behaviour of milter-greylist not to answer (or answer fast) when dumping? is de memory data locked when dumping, so no answers can be generated?

This data may help to other admins, if what i'm saying is true can it be on the official man page? this gave us several headaches. Also i can provide more info if anybody wants.

Regards,

----
Eduardo Casarero
Informatica Avanzada SRL
Email: eduardo.casarero@...
Tel: (054) 011-52353995 int. 207

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.