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 probably wouldn't use that, as I keep most config files in RCS, and
tend to have an emacs open on the config file and add things a bit at a
time.
I find milter-greylist's auto-rereading a bit aggressive, and think it
might be better to just do that on SIGHUP like inetd and others.
Then one could "/etc/rc.d/milter-greylist reload" or ".. check".
If there is auto-reload, it would be nice to read and validate it and
only swap it in if it's ok.
-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 probably wouldn't use that, as I keep most config files in RCS, and
tend to have an emacs open on the config file and add things a bit at a
time.
I find milter-greylist's auto-rereading a bit aggressive, and think it
might be better to just do that on SIGHUP like inetd and others.
Then one could "/etc/rc.d/milter-greylist reload" or ".. check".
If there is auto-reload, it would be nice to read and validate it and
only swap it in if it's ok.