Milter-greylist

Hello all,

   I see that milter-greylist refreshes the "running" configuration if
the greylist.conf file has changed, but only when it gets to process
the next email connection (or maybe even 1-2 emails after that).
On a not very busy relay this may happen after a substantial delay,
and only then I'd learn if the config is at all valid or some syntax
error was introduced.

   Is there a way to signal the daemon that it should re-read the new
configuration? Also, is it possible to not die in case of config
errors during this process, but just inform of the error and proceed
using old config data? :)

   Apparently, a SIGHUP commonly defined for config refresh and log
file reopening (for rotation, if any log-files are used) just kills
milter-greylist daemons.

   Did I miss something?

Thanks,
//Jim Klimov