similar to: Manual manipulation of Sieve files

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:

Hi Everyone, I have dovecot, postfix, roundcube and piegeonhole managesieve all working nicely together. Personal scripts defined in roundcube run without issue. I have configured the global sieve dir defined in 90-sieve.conf: sieve_global_dir = /var/lib/dovecot/sieve/global/ I pre-compiled the script in there: # ls -l /var/lib/dovecot/sieve/global/ total 8 -rw-r--r--. 1 root root 118 Sep 19

Hi again everyone, So I've finally got sieve integration happening on my? REHL Postfix/Dovecot server, with private user scripts happily running when users create them. (we user SquirrelMail, so the avelsieve plugin runs the sieve integration). Now I'd like to utilise additional per-user scripts (probably via sieve_before), but I've not been able to get my additional scripts to

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

Hello, I've ran into problem with Dovecot and dsync replication. Everything works perfectly, including replication of sieve scripts, except fact that if user activates the 'managesieve' ruleset (I'm using currently Roundcubemail) on "mail1" host, it wouldn't be activated on "mail2" host, by creating symlink ".dovecot.sieve ->

Hello list, I am starting to see these in maillog: dovecot: lmtp(31949, dwright): Error: kXK3KnTpXFXNfAAAU+Cu/Q: sieve: binary open: failed to open: open(/var/spool/mail/dwright/.dovecot.svbin) failed: Permission denied (euid=520(dwright) egid=12(mail) missing +r perm: /var/spool/mail/dwright/.dovecot.svbin, euid is not dir owner) But the directory /var/spool/mail/dwright is owned by

On Jan 1, 2015, at 9:50 AM, Stephan Bosch <stephan at rename-it.nl> wrote: > > Hmm. This smells like a bug. I notice that your modification times of > the .sieve and .svbin file are exactly the same (that is somewhat > unusual). I'm looking at a potential bug that would explain your problem. > > To confirm, could you try running sievec again, so that the .svbin is

On 05.08.2015 13:06, Steffen Kaiser wrote: > On Tue, 4 Aug 2015, Gerhard Wiesinger wrote: > >> >> I'm running dovecot in a classical vmail.vmail setup with pigeonhole >> and LMTP. Permission worked well in the initial setup but currently >> (maybe after Fedora 22 update) I'm having the following permission >> issue: >> >> lmtp(root):

Hello, I'm using dovecot 2.2.10 and roundcube (with managesieve enabled). Sieve filtering works well, as long the rule is written into ~/.dovecot.sieve (which is a link to ~/sieve/managesieve.sieve) When adding a new filter set (in roundcube) the script is written to ~/sieve/newfilterset.sieve. This script will not be executed. How can I solve this? I set sieve_dir = ~/sieve This should work,

Hello, I'm running dovecot in a classical vmail.vmail setup with pigeonhole and LMTP. Permission worked well in the initial setup but currently (maybe after Fedora 22 update) I'm having the following permission issue: lmtp(root): Error: 7fPZFOL9wFXePQAABcdabc: sieve: binary open: failed to open: open(/etc/dovecot/sieve_after.svbin) failed: Permission denied (euid=9999(vmail)

I have some global scripts that were running nicely. Then I opened one in an editor and (probably, but not 100% sure) mindlessly saved the file, even though I hadn't made any changes. Shortly after, Sieve errors started showing in the log: Error: 4k5JA74R/1TlIwABG/SpMA: sieve: binary save: failed to create temporary file: open(/usr/local/var/dovecot/sieve/script2.svbin.example.com.4139.)

Hello the list, I am trying to achieve filter processing using sieve, but i am not sure I can do what I want. I want to let the user decide to use my filtering script (sieve_after) or not.According to the documentation, i am trying to stop processing in user sieve script, but processing continue. I am using dovecot 2.2 (CentOS). My sieve configuration is:plugin { ? sieve =

Hi, After upgrading from dovecot 1.1 to dovecot 1.2.2 and the new sieve implementation (0.1.9), I'm having some strange problems. I'm including some general purpose scripts into my user script from sieve_global_dir. After some tests it seems that ths scripts get executed at random: sometimes the mail gets stored in the correct dir, and sometimes it goes to inbox. This also happens while

when .dovecot.sieve is a symlink (which it is in my case) a warning is written to the error log file, but it still works. Dec 12 10:02:33 managesieve(tester at domain.com): Warning: sieve-storage: Active sieve script symlink /srv/vmail/sieve/domain.com/tester/.dovecot.sieve is broken: invalid/unknown path to storage (points to ingo.sieve). root at

> > I have some global scripts that were running nicely. > > > > Then I opened one in an editor and (probably, but not 100% sure) > > mindlessly saved the file, even though I hadn't made any changes. > > > > Shortly after, Sieve errors started showing in the log: > > > > Error: 4k5JA74R/1TlIwABG/SpMA: sieve: binary save: failed to create

Hello! I have a problem with a sieve-script which works for one domain but not for another one. Both domains are hostet on the same server running dovecot and postfix. This is the script that works: require ["vacation"]; # rule:[Out of office] if true { vacation :days 1 :addresses "a.meyer at nimmini.de" :subject "absent" "Ich bin nicht da."; }

> > > > I have some global scripts that were running nicely. > > > > > > > > Then I opened one in an editor and (probably, but not 100% sure) > > > > mindlessly saved the file, even though I hadn't made any changes. > > > > > > > > Shortly after, Sieve errors started showing in the log: > > > > > > >

On Jan 1, 2015, at 8:10 AM, Stephan Bosch <stephan at rename-it.nl> wrote: > > Could you enable mail_debug? That should show why it is trying to > recompile the Sieve script. Well, that it does! And it's saying the script is "not up to date" and tries to recompile it. However, I'm not sure why it would say it's NOT up to date, it most certainly was

On 1/1/2015 4:17 PM, Robert Blayzor wrote: > On Jan 1, 2015, at 9:58 AM, Robert Blayzor <rblayzor.bulk at inoc.net> wrote: >>> Hmm. This smells like a bug. I notice that your modification times of >>> the .sieve and .svbin file are exactly the same (that is somewhat >>> unusual). I'm looking at a potential bug that would explain your problem. >>>

Hi all I have dovecot-lda set up to run as vmail:vmail, with some sieve scripts in /var/lib/dovecot/sieve. The sieve scripts fail to be found with the following (detailed and very helpful) error message: Oct 14 16:13:33 gatekeeper dovecot[8109]: lda(minfrin at example.com)<8109><ZJ9nMo0Hh1+tHwAAKdTwig>: Error: sieve: file storage: Failed to stat sieve storage path: