similar to: Why is Sieve trying to re-compile global scripts?

> > 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

> > > > 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: > > > > > > >

> > > > > 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: >

> > > 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:

On 3/11/2015 2:10 AM, E.B. wrote: > 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

On 3/11/2015 11:10 AM, Olaf Hopp wrote: > Please see the thread with subject > "Sieve permissions issue following update" > I tested sucessfully a developper issue last month > on the hint of Stephan. Yesterday I started to test the currenr RCs. > > First I was disappointed, because the error seems to persist. > So I double checked everything, recreated / recompiled

> Since E.B. still got an obscure debug message about metadata not being > up to date, I added debug lines to the remaining places where this could > emerge (currently only available from hg). Using hg from just now - first line looks like what you want: dovecot: lmtp(testuser at example.com): Debug: U5ZtLH8IAVXydgNAM/SpMA: sieve: file script: Binary reports different script location

On 3/11/2015 3:16 AM, E.B. wrote: >>>> Last time I had a few stupid problems in the releases, so >>>> I'll follow >>>> Timo's example and I release an RC first. >>>> >>>> The highlights include the implementation of the index and >>>> metadata >>>> extensions. Quite a few bugs are fixed as well.

On 3/10/2015 8:11 PM, E.B. wrote: >> Last time I had a few stupid problems in the releases, so >> I'll follow >> Timo's example and I release an RC first. >> >> The highlights include the implementation of the index and >> metadata >> extensions. Quite a few bugs are fixed as well. > When I compiled and installed this, Sieve scripts were being

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

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)

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 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

On Dec 10, 2014, at 1:52 AM, Steffen Kaiser <skdovecot at smail.inf.fh-brs.de> wrote: > >> 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: > > Actually this "ls" output and the last

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

-------- Original Message -------- Subject: Re: Sieve permissions issue following update From: Steffen Kaiser <skdovecot at smail.inf.fh-brs.de> To: David Gessel <gessel at blackrosetech.com> Date: Wed Dec 10 2014 09:52:57 GMT+0300 (Arabic Standard Time) > > Actually this "ls" output and the last sentence does not indicate that the Sieve script had been compiled: a)

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):

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. >>>

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

> >>> When I compiled and installed this, Sieve scripts were being ignored. Not > >>> sure if it's my own stupid mistake, but when I put v0.4.6 back in place, it > >>> worked fine. No configuration changes, only make install on the different > >>> sources and restart dovecot. > >> Could you show your dovecot -n output? > >> >