search for: sievec

How do you compile global scripts using the sievec command without making the script directory owned (and group writable) by the vmail user? http://wiki2.dovecot.org/Pigeonhole/Sieve/Usage # cd /etc/dovecot/sieve/before/ # (edit some script like spam.sieve that runs for everyone) # /usr/local/bin/sievec spam.sieve spam.svbin sievec(root): Error...

Hello list, How can I compile sieve script under new 0.2.2 version from comandline? Under root: #sievec default-before.sieve sievec(root): Error: user root: Initialization failed: Namespace '': mkdir(/root/data) failed: Permission denied (euid=8(mail) egid=12(mail) missing +w perm: /root, euid is not dir owner) sievec(root): Fatal: Invalid user settings. Refer to server log for more informati...

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 consider this a bug report. :) Good luck, Reio

On Fri, May 31, 2019 10:18 am, Ralph Seichter via dovecot wrote: > * Voytek Eymont via dovecot: > Try runing "sievec -u {your_linux_user} /path/to/whatever.sieve" from a > shell and check the resulting error messages. Raplh, thanks so, am I'm missing sql lookup for sieve...? # sievec -u voytek dovecot.sieve sievec(voytek)<9667><>: Error: user voytek: Auth USER lookup failed sievec(root...

It has been running flawlessly for quite some time until the update. Global scripts were compiled: /usr/local/etc/dovecot/sieve # ls 10-move-spam.sieve 10-move-spam.svbin However, I ran sievec again and tried saving a modified script and got the same: shiofuki dovecot: lda(gessel at blackrosetech.com): Error: sieve: binary save: failed to create temporary file: open(/usr/local/etc/dovecot/sieve/10-move-spam.svbin.shiofuki.blackrosetech.com.96421.) failed: Permission denied (euid=5000(vm...

Hello, I'm trying to figure out if this is a configuration issue or an actual bug. Dovecot does start, but if anybody tries to log in or if you run sievec you get an assertion fail and a coredump. --- sievec(root): Panic: file mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns != NULL) sievec(root): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9c3a2) [0x7ff70e2133a2] -> /usr/lib/dovecot/libdovecot.so.0(+0x9c429)...

My sieve problem ended up a permissions problem. I ran sievec as root and .svbin needs vmail:mail ownership. I could always just add the chown command to my process, but I wonder if there is some 'clean' way to run sievec as user vmail while logged in as root? thanks

...similar to the following snippet if not anyof (address :is ["from","cc"] ["...", ..., "... at ... GARBAGE", ...] { fileinto "inbox.Trash"; stop; } Note the extra line break before GARBAGE. This script is obviously broken, but gets accepted by sievec and only fails later, at runtime with line X: error: found stray carriage-return (CR) character in quoted string started at line X. So, the question is whether line breaks in strings are allowed in general and the runtime error is unavoidable, or should sievec return an error? Best regards,...

Hi, when switching from Dovecot 1.1 + cmusieve to Dovecot 1.2 + sieve I stumbled upon the following problem: My sieve files, generated with Dovecot 1.1's managesieve, did not compile anymore with sieve's sievec. The error message was: error: end of file before end of hash comment. Looking a bit closer I found that the last line, which was a comment, did not have a trailing newline. Adding a newline fixed the problem. I do not know if Dovecot 1.2's managesieve behaves differently, but the upgrade f...

...e this is the error that i came accross: /bin/bash ../../libtool --tag=CC --mode=link gcc -std=gnu99 -O3 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I../.. -export-dynamic -o sievec sievec.o ../../src/lib-sieve/libdovecot-sieve.la ../../src/lib-sieve-tool/ libsieve-tool.la -ldovecot-storage -ldovecot-lda -L/usr/local/lib/dovecot -ldovecot -lrt libtool: link: gcc -std=gnu99 -O3 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -W...

...permission in /var/cache/sieve/. h01:/var/cache/sieve# ls -la total 16 drwxr-xr-x 2 ecp ecp 4096 Mar 31 21:32 . drwxr-xr-x 10 root root 4096 Mar 31 20:14 .. -rw-r--r-- 1 ecp ecp 88 Mar 31 21:32 mailtest1 at domain.com.sieve -rw-r--r-- 1 ecp ecp 132 Mar 31 21:32 mailtest1 at domain.com.sievec When deliver runs it logs this error: open(/var/cache/sieve/mailtest1 at domain.com.sievec.tmp) failed: Permission denied This indicates deliver tries to compile the script, even though the compiled version already is there. To verify I tested another case. I make the compiled script immutable...

...+w perm: /etc/dovecot/sieve, dir owned by 0:0 mode=0755) Jun 25 14:29:43 mail dovecot: lda(2001): Error: sieve: the lda sieve plugin does not have permission to save global sieve script binaries; global sieve scripts like /etc/dovecot/sieve/default need to be pre-compiled using the sievec tool Due to the lack of permissions, this is of course expected. However, when I then try to precompile the script using sievec, that also fails: # sievec /etc/dovecot/sieve/default sievec(root): Error: sieve: binary save: failed to create temporary file: open(/etc/dovecot/sieve/default.svbin.ma...

Dovecot 2.2.36 + Pigeonhole 0.4.24 Is this an intended behavior? ``` # service dovecot status dovecot is stopped # doveconf mail_plugins mail_plugins = stats # ls foo.* foo.sieve # sievec foo.sieve sievec(root): Error: stats: open(/var/run/dovecot/stats-mail) failed: No such device or address # echo $? 0 # ls foo.* foo.sieve foo.svbin ``` -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: https://www.OSSTech.co.jp/ -- GitHub Home: https:...

> On 5 Nov 2019, at 9.53, Reio Remma via dovecot <dovecot at dovecot.org> 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 instead of first.svbin, thus destroying the source of second.sieve. > > Please consider this a bug report. :) Not a bug. Works as documented: # sievec Usage: sievec [-c <config-file>] [-d] [-D]...

As far as I can tell, 'sievec' always exits with '0' whether there is an error or not. If that is correct, I believe it should be modified to exit with some other code if the conversion and writing of the new file are not completed successfully. I have written a few script files and a 'make' file specificall...

There is a roff typo in pigeonhole's sievec.1.in. Roff treats the leading apostrophe on line 54 as an invalid command and produces bad output: dump to be written to stdout. The out-file argument may also be omitted, which has the same effect as for a com- piled Sieve binary file. Note that...

...uot;Spam"; stop; } EOF chown -R vmail:mail /home/sieve But in 90-sieve.conf there is the comment: # A path to a global sieve script file, which gets executed ONLY # if user's private Sieve script doesn't exist. Be sure to # pre-compile this script manually using the sievec command line # tool. #sieve_global_path = /var/lib/dovecot/sieve/default.sieve Do I run sievec on this script? And I found the following comment on a blog, about 3 years old: 2: Having a user-defined sieve script will cancel out the global script for redirecting spam. In the dovecot.conf,...

...erm: /usr/local/etc/sieve/after, euid is not dir owner) acamail dovecot: lda(xxxxx at xxxxxx): Error: sieve: the lda sieve plugin does not have permission to save global sieve script binaries; global sieve scripts like /usr/local/etc/sieve/after/after.dovecot.sieve need to be pre-compiled using the sievec tool So i tried to recompile script using sievec like: sievec /usr/lcaol/etc/sieve/after/after.dovecot.sieve but i get: sievec(root): Error: user root: Initialization failed: Initializing mail storage from mail_location setting failed: stat(/root/Maildir) failed: Permission denied (euid=40(vmail...

since moving/upgrading system I've noticed I no longer get sieve script compiled, there is no dovecot.svbin created in /var/vmail/vmail1/sbt.net.au/voytek at tld.au/sieve what am I missing, how to check ? also, looking at sieve.log, I see a lot of May 31 06:32:50 lda(voytek at sbt.net.au)<1234><c4aVBfI98FzSBAAAyLbbsQ>: Error: sieve: Failed to initialize script execution: Invalid

...F > > chown -R vmail:mail /home/sieve > > But in 90-sieve.conf there is the comment: > > # A path to a global sieve script file, which gets executed ONLY > # if user's private Sieve script doesn't exist. Be sure to > # pre-compile this script manually using the sievec command line > # tool. > #sieve_global_path = /var/lib/dovecot/sieve/default.sieve > > Do I run sievec on this script? Yes. > And I found the following comment on a blog, about 3 years old: > > 2: Having a user-defined sieve script will cancel out the global > script f...