Re: sievec *.sieve problem.

2019-11-05 Thread Reio Remma via dovecot
On 05/11/2019 10:03, Sami Ketola via dovecot wrote: On 5 Nov 2019, at 9.53, Reio Remma via dovecot > wrote: Hello! For the second time I've tripped onto this banana peel. :) I had 2 sieve files in a directory that I wanted to compile: sievec *.sieve The result

Re: sievec *.sieve problem.

2019-11-05 Thread Sami Ketola via dovecot
> On 5 Nov 2019, at 9.53, Reio Remma via dovecot wrote: > > Hello! > > For the second time I've tripped onto this banana peel. :) > > I had 2 sieve files in a directory that I wanted to compile: > > sievec *.sieve > > The result of this is that first.sieve is compiled into second.sieve inst

sievec *.sieve problem.

2019-11-04 Thread Reio Remma via dovecot
Hello! For the second time I've tripped onto this banana peel. :) I had 2 sieve files in a directory that I wanted to compile: sievec *.sieve The result of this is that first.sieve is compiled into second.sieve instead of first.svbin, thus destroying the source of second.sieve. Please consi