similar to: Sieve 0.2.2 how to use sievec

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

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.

Dear all, I stumbled upon the following behaviour of Pigeonhole, which I consider to be problematic. A user deployed a Sieve script 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

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

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: sieve: binary save: failed to create temporary

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 specifically for sievec. The inability to get an accurate exit code is

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.

I am building a new mailserver on Centos7. My sieve is created with: mkdir /home/sieve cat <<EOF>/home/sieve/globalfilter.sieve || exit 1 require "fileinto"; if exists "X-Spam-Flag" { if header :contains "X-Spam-Flag" "NO" { } else { fileinto "Spam"; stop; } } if header :contains "subject"

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 this option is not The output should be:

Hello, sievec segfaults when it reads a file. I've tried with both the standard and gold linker. I've tried with various sieve files and they all make it crash. I've compiled pigeonhole with -ggdb, but I'm not getting much info Program received signal SIGSEGV, Segmentation fault. 0x0000000800b8e587 in strlen () from /lib/libc.so.7 (gdb) bt full #0 0x0000000800b8e587 in strlen ()

Hi, I upgraded a server from an old Linux distribution to a much newer one. In the process, Dovecot got upgraded from v1 to v2. By mistake, I deleted the .sieve plaintext file with all the Sieve filters, but I still do have the .sievec compiled binary. Is there any way to dump the binary file back into plaintext format? Keep in mind, I'm running v2 now, and the binary was made on a v1

I'm just getting familiar with Dovecot. I get this error when I send mail to a mailbox that is over quota. I have no problem with the way quota is working and I have no problem with the sieve script detecting spam and delivering it to the Spam folder. Just trying to figure out why I get this error when quota is involved: Error: sieve_execute_bytecode(/var/sieve/global.sievec) failed See logs

I am trying to implement vacation with sieve in dovecot, but each time I try to use a sieve rule that sends a mail, like vacation or reject, I obtain this error code_ sieve_execute_bytecode(/var/vmail/domain1/user/dovecot.sievec) failed Checking syslog I found this message: sieve runtime error: Reject: No return-path for reply Googling I found a report of a problem like this but I can't

Hello list, I have noticed strange dovecot behavior with exim system-filter. I'm using exim+dovecot setup. My exim configuration have system filter enable, which restrict some attachments, like exe, vbs etc. When message with forbidden attachment received, exim accept the message, then construct bounce-message(Reject reason + original message) and returns it to sender. Trying to deliver such

Hello list, I have noticed that sieve vacation action breaks some non-english letters in the subject. I tested with russian language, if subject contains letters from specific diapason russian alphabet, the message received with unreadable subject, but text in the body with the same letters looks ok. Here is example of full subject header, it contains russian alphabet: Subject:

> 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

(Please keep me CC'd, I'm not subscribed) Hi folks, I'm using dovecot 2.1.7 (from Debian stable) with sieve. I have default sieve script configured, which lives in /etc/dovecot/sieve. I use dovecot-lda running under the virtual-mail user, which does not have write access to the /etc/dovecot/sieve directory. Now, when a mail gets delivered, I get the following message in my logs.

I'm getting this error when compiling .dovecot.sieve: $ /usr/libexec/dovecot/sievec .dovecot.sieve .dovecot.sievec Info: line 3: fileinto require missing Unable to parse script: script errors: line 3: fileinto require missing .dovecot.sieve just looks like this: $ cat .dovecot.sieve if header :contains ["List-Id"]

Op 3/16/2017 om 10:20 PM schreef Robert Moskowitz: > I am building a new mailserver on Centos7. > > My sieve is created with: > > mkdir /home/sieve > cat <<EOF>/home/sieve/globalfilter.sieve || exit 1 > require "fileinto"; > if exists "X-Spam-Flag" { > if header :contains "X-Spam-Flag" "NO" { > } else { >

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