19 Dec
2017
19 Dec
'17
12:44 p.m.
On December 19, 2017 at 5:06 AM Garth Corral gcorral@abode.com wrote:
In looking at this further, I’m not seeing how this can be configured as documented and still work.
The sieve_pipe_socket_dir setting, as the documentation suggests, appears to be used by the plugin to construct a path to find the “script” (the socket in this case), and it is always relative to base_dir and must include the contents of sieve_pipe_socket_dir.
Hi!
The socket_dir setting is only needed if you actually want to use unix sockets for pipe scripts. It's not required for using this plugin.
Aki
Thanks in advance,
Garth