similar to: Sieve problems - compiled script does not get updated

Hello, I'm trying to setup dovecot with sieve support in a way where all sieve scripts are precompiled. All sieve scripts are in /var/cache/sieve/. I believe I discovered a bug here. I describe below how to reproduce it. Dovecot and the user that deliver runs as do not have write permission in /var/cache/sieve/. h01:/var/cache/sieve# ls -la total 16 drwxr-xr-x 2 ecp ecp 4096 Mar 31

Hello, I'm using dovecot 1.0.3 and Dovecot Sieve plugin 1.0.2. Sieve script works fine with normal addresses, like user at domain.., and messages marked with "X-Spam-Flag: YES" are delivered directly to INBOX.Spam. To make deliver understand recipient_delimiter I tried two methods, the first one as per wiki (tweaking postfix master.cf), and the second one by tweaking

Hi list Trying to get sieve for 1.2 running (dovecot sieve, not cmusieve) I'm running on centos 5.4 64bit, dovecot rpms installed from http://atrpms.net/dist/el5/dovecot/ ( dovecot-1.2.7-0_102.el5.x86_64.rpm and dovecot-devel-1.2.7-0_102.el5.x86_64.rpm ) I pulled the sieve sources ( hg clone http://hg.rename-it.nl/dovecot-1.2-sieve ) autogen.sh ./configure

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.

Hello! Is there a chance to have sieve working with dovecot version 1.0.5? /usr/lib/dovecot looks like this: -rwxr-xr-x 1 root root 43932 22. Sep 2007 checkpassword-reply -rwxr-xr-x 1 root root 538996 22. Sep 2007 deliver -rwxr-xr-x 1 root root 127728 22. Sep 2007 dict -rwxr-xr-x 1 root root 270248 22. Sep 2007 dovecot-auth -rwxr-xr-x 1 root root 43952 22. Sep 2007 gdbhelper -rwxr-xr-x 1

I have the following global cmusieve scripts defined in /etc/dovecot/sieve, which is owned by the user deliver is run (virtual) as defined in the lda session of dovecot.conf: global-spam.script ====================================== require ["fileinto"]; # Move spam to spam folder if header :contains "X-Spam-Level" "********************" { fileinto

Hello, I try to migrate to dovecot-lda from procmail, but some script can't run under lda cmusieve plugin. dovecot version: dovecot-1.0(debian) revelant config dovecot.conf: protocol lda { postmaster_address = postmaster at wizard.dunanet.hu hostname = wizard.dunanet.hu mail_plugin_dir = /usr/lib/dovecot/modules/lda #sendmail_path = /usr/lib/sendmail auth_socket_path =

How can I do this with Sieve? I have a script like this: if header :value "ge" :comparator "i;ascii-numeric" ["X-Spam-Score"] ["25"] { discard; stop; } elsif header :value "ge" :comparator "i;ascii-numeric" ["X-Spam-Score"] ["5"] { fileinto "Junk"; stop; } else {

Hi, I'm having problems unsubscribing from public folders - nothing seems to happen when I do that (from Thunderbird, Squirrelmail or telnet). I'm using Dovecot 1.2.11. I remember that this worked when I was using version 1.1.7. Here is an extract from an imap session: 3 unsubscribe "Public-NIB/archive/older" 3 OK Unsubscribe completed. 6 lsub ""

Hi, all. I use a global sieve script and include user's personal sieve script in it, but it doesn't run while user's sieve script not exist. Why not just ignore this error and continue read and execute the rest of sieve rules? My global script: ---- require ["include"]; include :personal ".dovecot.sieve"; ---- Sieve log while user's personal sieve script

Does the keyword/action discard work by default or is there something I have to do in the configuration to get to work... maybe I missed something on http://wiki.dovecot.org/LDA/Sieve I have the following rule: if anyof ( header :contains ["Subject"] ["Test Discard"] ) { discard; stop; } but it delivers to INBOX with or w/o the "stop;". If I change

Hello This is my dovecot.conf : /etc/dovecot/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.info protocols: imap imaps managesieve login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_location:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, I would like to use managesieve protocol and cmusieve plugin at the same time. I have used the cmusieve plugin for years and I now also enabled the managesieve system. I got the managesieve system working but when I activate the managesieve filter for the user the cmusieve sieve filter is not used anymore. How can I have both sieve

Hi, all. I use dovecot-1.1.1 and dovecot-1.1.5 which built by atrpms, and i use 'include' command to include two/several personal sieve rule file, but if either of these personal sieve rule files is not exist, sieve_execute_bytecode failed. How can i make it just skip the non-exist personal sieve rule file, and continue to try to include next sieve rule file? Thanks very much. :) In

In Dovecot 1.1.11 cmusieve is apparently integrated in the Ubuntu 9.10 package "dovecot-common" since the files are there. I am wanting to right now just do a very basic test of the setup to see how it runs before doing more sophisticated steps that could obscure any errors or bugs (e.g. unit testing). So I took the following example sieve script from the wiki1 documentation: require

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 With the sieve plugin trying to redirect or send vacation reply I'm getting the following error: Aug 19 13:12:52 goku deliver(joeblow): [ID 619685 mail.info] Module loaded: /use rM/mail-services/dovecot/lib/dovecot/lda/lib90_cmusieve_plugin.so Aug 19 13:12:52 goku deliver(joeblow): [ID 848615 mail.info] mbox:

Hello Dovecot users, Finally, after little more than a year, I finished the first release of the new Sieve implementation for Dovecot. The main reason for rewriting the Sieve engine is to provide more reliable script execution and to provide better error messages to users and system administrators. Also, since the Sieve language evolves quickly, with new language extensions published every

Hello Dovecot users, Finally, after little more than a year, I finished the first release of the new Sieve implementation for Dovecot. The main reason for rewriting the Sieve engine is to provide more reliable script execution and to provide better error messages to users and system administrators. Also, since the Sieve language evolves quickly, with new language extensions published every

Hello Dovecot users, Since the first release of the new Sieve implementation, not that many bugs were reported. This is probably due to the fact that it is not tried yet by that many people. In the mean time, I did find and fix some more bugs myself, I adapted to changes in Dovecot, wrote some more documentation and started work on the enotify extension. Both Sieve and ManageSieve were changed

I have install dovecot and sieve and it doesn't appear to be working. Below is my dovecot.conf Are there some debugging settings I can use to test if dovecot is linking with sieve properly. Nothing appears to show up in the logs start dovecot.conf ======================= cat /usr/local/etc/dovecot.conf base_dir = /var/run/dovecot/ auth_verbose=yes auth_debug=yes mail_debug=yes