Re: sieve_pipe_socket_dir not created at startup for configured pipe service

2017-12-23 Thread Stephan Bosch
Op 12/18/2017 om 1:51 AM schreef Garth Corral: > Hi, all > > I’m new to the list but not to dovecot. I’ve been using it in a basic > configuration for some time, but finally decided to tweak my deployed system > to take advantage of some more dovecot features. In particular I’m trying to > set

Re: sieve_pipe_socket_dir not created at startup for configured pipe service

2017-12-19 Thread Aki Tuomi
> On December 19, 2017 at 5:06 AM Garth Corral 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 fi

Re: sieve_pipe_socket_dir not created at startup for configured pipe service

2017-12-18 Thread Garth Corral
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

sieve_pipe_socket_dir not created at startup for configured pipe service

2017-12-17 Thread Garth Corral
Hi, all I’m new to the list but not to dovecot. I’ve been using it in a basic configuration for some time, but finally decided to tweak my deployed system to take advantage of some more dovecot features. In particular I’m trying to set up pigeonhole to implement spam retraining with imapsiev