Milter-greylist

17 \u0444\u0435\u0432\u0440\u0430\u043b\u044f 2016�\u0433. 15:13:09 CET, "Bob Friesenhahn bfriesen@... [milter-greylist]" <milter-greylist@yahoogroups.com> \u043f\u0438\u0448\u0435\u0442:
>This morning I noticed that milter-greylist (4.5.16 running on OmniOS 
>r151016) had stopped writing to its dedicated log file on the 13th. 
>I restarted it and then it resumed writing the log file.  It seems 
>that milter-greylist did not resume writing its log file on a day when 
>I was doing some experimentation with various configurations and 
>restarting it often.
>
>Are there any known issues with milter-greylist writing its log file?
>
>The directory ownership is sufficient that milter-greylist is able to 
>write its greylist.db in the same directory, bug the log file is owned 
>by root.
>
>Thanks,
>
>Bob

Actually, you "should not have to" restart it for new configs: when processing a new message, MGL starts by verifying if its config is up to date, and reloads/reapplies it if it is not. It has a check (-c ?) CLI option to validate a new candidate config before you feed it into/replace the live cfg file, so the service is uninterrupted as you change it.

Regarding logs: do you start MGL as root and then drop (via config user), or start as non-root, or is this close to what you changed recently? ;)

Jim

Jim
--
Typos courtesy of K-9 Mail on my Samsung Android