Milter-greylist

Emmanuel Dreyfus a \ufffdcrit :
> On Wed, Sep 24, 2008 at 09:01:24AM +0200, Benoit Branciard wrote:
>> The attached "update-greylistconf" script is the thing I use for this purpose.
> 
> I wonder if a command line flag could not help here: milter-greylist -e
> would edit a copy of greylist.conf with your favourite $EDITOR, validate
> it, and replace the original if the new file is fine. 
> 
> That should not be very difficult to implement. Opinion, anyone?
> 

I don't consider this "the rignt way".

1) It add some (minor) complexity tho the daemon itself, while the same 
goal could be achieved by an external program.

2) It is "interactive-oriented" and adds nothing for scipted tasks.

3) It depends on the $EDITOR variable, which in my case never points to 
the right "favourite" editor as I'm too lazy to update it on every 
server I administer (how a nightmare to be sure this variable is OK for 
my personal account, for the root account, in a login/not login shell...).


Another approach which seems rather cute to me would be to handle this 
in the daemon starting script (/etc/init.d/milter-greylist on usual 
System V Unixes):
- "start" command: validates /etc/greylist.conf with "-c", and in case 
of success, copies it to /var/lib/milter-greylist/greylist.conf and 
starts the daemon;
- "stop" stops the daemon (as usual)
- "reload" validates /etc/greylist.conf with "-c", and in case of 
success copies it to /var/lib/milter-greylist/greylist.conf (without 
restarting the daemon)

And of course, milter-greylist would be compiled with a config-file path 
set to /var/lib/milter-greylist/greylist.conf.

Not very difficult to do, and well-suited for packaging milter-greylist 
for various distributions (Debian...)

I could write it some day when I find time to do it.

-- 
Ce message a ete verifie par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a ete trouve.