Milter-greylist

Running 3.0rc4, it looks like I got my permission problems solved.

How does milter-greylist react to signals?  I sent it a HUP signal
to reread the greylist.conf file, and it went away.  Oops.  Does
this work?

It would be nice if a HUP reread the config file and another signal
(SIG_USR1?) would dump the db file on demand.

Jeff Earickson
Colby College

Jeff A. Earickson <jaearick@...> wrote:

> How does milter-greylist react to signals?  I sent it a HUP signal
> to reread the greylist.conf file, and it went away.  Oops.  Does
> this work?

Is there any volunteer to start the milter-greylist FAQ? That one is our
#1.

The milter API says libmilter catches the signal. milter-greylist cannot
use them. 
 
> It would be nice if a HUP reread the config file and another signal
> (SIG_USR1?) would dump the db file on demand.

config is reloaded when the two conditions are met
1) the file has changed
2) a new SMTP connexion reaches the FROM stage

The on-demand dump could be implemented by having a command line tool
communicating with milter-greylist through a socket interface. A good
idea for later.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...