> On 13 November 2018 at 20:38 Lionel Elie Mamane wrote:
>
>
> On Tue, Nov 13, 2018 at 07:10:47PM +0200, Aki Tuomi wrote:
> > Did you look at the server logs as suggested by the logfile?
>
> Yes. The server log is in my first email, where I called it "dovecot
> debug log". Sorry the informati
On Tue, Nov 13, 2018 at 07:10:47PM +0200, Aki Tuomi wrote:
> Did you look at the server logs as suggested by the logfile?
Yes. The server log is in my first email, where I called it "dovecot
debug log". Sorry the information is over several emails.
--
Lionel
I found a work-around. I added an :output option to the execute
command, and then it works like a charm.
I've run the whole dovecot-lda under strace (without the :output
option, when it shows the problem):
6410 stat("/usr/local/lib/dovecot/sieve-execute/foofilter",
{st_mode=S_IFREG|0755, st_siz
Did you look at the server logs as suggested by the logfile?
Aki
> On 13 November 2018 at 18:52 Lionel Elie Mamane wrote:
>
>
> And the Sieve script:
>
> --- start sieve script -
> require ["vnd.dovecot.execute", "fileinto", "mailbox", "vnd.dovecot.debug"];
>
> debug_log "about t
And the Sieve script:
--- start sieve script -
require ["vnd.dovecot.execute", "fileinto", "mailbox", "vnd.dovecot.debug"];
debug_log "about to execute";
if not execute :pipe "foofilter" {
debug_log "if condition fulfilled";
fileinto :create "test-spam";
debug_log "about to stop
Hi,
Running dovecot 2.2.27 (c0f36b0) on Debian GNU/Linux stable (version
9.6), I'm trying to use the execute command in a sieve script, with
direct execution (not service socket).
The script is executed, and returns (the process exits), but the
dovecot-lda process seems to not notice, and thinks
