Milter-greylist

1) Do greylist.conf's parametets accept "s" (for seconds) and "w"
(for weeks) suffixes as well as in command-line?
If yes, I believe they should be mentioned in greylist.conf(5).

And several features which we are missing of.

2) Have you ever thought about such feature as limiting resources
taken by milter-greylist for keeping tuples?  It would be nice to
have one, for example, a simple limit of the number of tuples which
can be hold in memory (if the limit reaches milter-greylist should
optionally remove the oldest tuples or just approve connections).

3) Supporting DB4 for getting the actual whitelist is very much
needed (it's already in TODO list, I know).

4) Dumping database on exit whould be great too.  Problems are very
rare and the database is very big, so we dump it once in two hours.
It is sad to lose records during, say, system reboots.

With the best regards,
Denis Solovyov

Denis Solovyov wrote:
 > 4) Dumping database on exit whould be great too.  Problems are very
 > rare and the database is very big, so we dump it once in two hours.
 > It is sad to lose records during, say, system reboots.

milter-greylist already does that.
When I send a SIGTERM, it first writes the curent list to
the dump file before it exits (takes about half a minute
on my machine).

Best regards
   Oliver

-- 
Oliver Fromme,  secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

"The scanf() function is a large and complex beast that often does
something almost but not quite entirely unlike what you desired."
        -- Chris Torek