On Tue, Dec 20, 2005 at 11:44:09AM +0100, Michael Menge wrote: > >signal handling is forbidden by the milter API. We have a callback on exit, > >but AFAIK that does not work if you get a deadly signal. > Is there a SIGNAL which is not "deadly" and will call the atexit callback? It does not change anything is the signal is not fatal: we cannot catch it anyway. The only way to solve that problem is to find a signal that is catched by libmilter and where the signal handler calls exit(). > >If we want to remote control milter-greylist dumping, we need to have > >a socket control. The easiest way is to reuse the MX sync protocol and > >add a dump command. That would be easy. > This may be a work around, but you need a telnet connection to tell > milter-greylist to dump his db Not nescessarily, we could have a command line tool that does just that. something such as: mgctl 127.0.0.1 dump > With about 180.000 eMails per Day like oure site this may be a problem. > If you add a dump and exit funktion to MX sync there could be some > security problems. Oh, you mean a rogue client requesting continous dumps? Then it's time to use RSA keys... -- Emmanuel Dreyfus manu@...
Message
Re: [milter-greylist] dump greylist.db on SIGTERM
2005-12-20 by Emmanuel Dreyfus
Attachments
- No local attachments were found for this message.