|
From: Lionel B. <lio...@bo...> - 2004-12-15 07:30:20
|
This is roughly organised by priority. Did I miss something ? -- BEGIN 1.4.x - fix EGID bug (done in CVS), - allow distributing whitelists from a central point . reload whitelists on SIGUSR1 (done in CVS, not tested) . separate script which updates the whitelist and calls SIGUSR1 - send mails (adjustable rate) to postmaster when the database goes down and comes back - make maint_delay configurable 1.5.x development releases - use time units everywhere to make configuration easier (add safety barriers ?) - experiment with SPF support - consider optin/optout (is it easy to do with Postfix? Then provide an HOWTO else code it in SQLgrey and document it) - support migrating from another greylister by calling it to learn its auto-whitelists - external cleanup process/experiment with an adaptative cleanup algorithm As soon as available... - gather enough perf data to decide on indices to add -- END I thought that starting with 1.4.0 development would slow down :-) People asking for whitelist reloads probably noticed that I don't use SIGHUP for whitelists reloading as initially planned. This is because when I implemented the reloading code in SQLgrey I discovered that SIGHUP handling was done by Net::Server. I tried to use the appropriate hooks to reload the whitelists but it seems Net::Server::Multiplex SIGHUP handling is buggy (seems there's a race condition related to the pidfile removal when it restarts the process that leads to a complete crash), so I went the USR1 way... When the example script and the distribution server are both ready I'll release 1.4.1. Lionel. |