On Wed, Dec 21, 2005 at 08:47:26AM +0100, Michael Menge wrote: > >>>signal handling is forbidden by the milter API. We have a callback on > >>>exit, (snip) > I havent found any hint that signal handling is forbidden by the milter > API, AFAIK they say only that lib milter takes care of signal handling Which means the milter does not. > In the Doc of libmilter they mention only Stop and Abort. If Abort is > cought xxfi_abort callback is invoked. It's invoked for each message that is aborted, and if the milter gets SIGABRT, all messages will be aborted. It could make sense to count the number of messages been handled, and if the count reach zero in xxfi_abort, make a dump. > The problem is that at the momen you can only add and remove db entries > with the MX sync protocol. Even if someone wants to use this they cannot > do mutch harm. Yes, this is why I did not add any authentication mecanism: an attacker cannot do anything through MX sync it could not do by simply sending an e-mail. -- Emmanuel Dreyfus manu@...
Message
Re: [milter-greylist] dump greylist.db on SIGTERM
2005-12-21 by Emmanuel Dreyfus
Attachments
- No local attachments were found for this message.