dovecot - Mar 2015 - Why is Sieve trying to re-compile global scripts?

> Not sure how I got it to go away last time.
Might have gotten it to go away by deleting the scripts, causing an
email delivery, THEN creating the scripts again.  

Although I think my ideas are all flawed:

I can delete the scripts and recreate and recompile all in the same
minute and I don't get errors.

I can cause the error to happen again by editing and recompiling
one of the files, *whether or not in the same minute* and I do get
the error.

This time around, deleting the files and recreating/recompiling
them even without an email delivery in between seems to fix
the error.

Might be unpredictable caching.  Might be the error didn't go away
last time I recreated due to different methods of creating the files.
Who knows, I think I should give up and stop spamming the list
with uneducated guesswork.

On 03/11/2015 07:17 AM, E.B. wrote:
>
> Might be unpredictable caching.  Might be the error didn't go away
> last time I recreated due to different methods of creating the files.
> Who knows, I think I should give up and stop spamming the list
> with uneducated guesswork.
No - no spam at least for me.

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 everything
an the error went away. So I thought it was mistake on my side.
I gave Spephan postive feedback. And I'm waiting for the final release
for my production server.

But when I read your mails, I'm not feeling happy.
I think it's a kink of luck/voodoo/whatever.

What you must do, I think, is to compile the sieve script with the
exact version running afterwards.
And I think you should the remove the compiled .svbin files
before recreating them again. Don't overwrite them with the compiler.

I think I'll also dig into this any further today.

Olaf

-- 
Karlsruher Institut f?r Technologie (KIT)
ATIS - Abt. Technische Infrastruktur, Fakult?t f?r Informatik

Dipl.-Geophys. Olaf Hopp
- Leitung IT-Dienste -

Am Fasanengarten 5, Geb?ude 50.34, Raum 009
76131 Karlsruhe
Telefon: +49 721 608-43973
Fax: +49 721 608-46699
E-Mail: Olaf.Hopp at kit.edu
atis.informatik.kit.edu

www.kit.edu

KIT - Universit?t des Landes Baden-W?rttemberg und nationales Forschungszentrum
in der Helmholtz-Gemeinschaft

Das KIT ist seit 2010 als familiengerechte Hochschule zertifiziert.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5214 bytes
Desc: S/MIME Cryptographic Signature
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20150311/7d6b3cc8/attachment.p7s>

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 everything
> an the error went away. So I thought it was mistake on my side.
> I gave Spephan postive feedback. And I'm waiting for the final release
> for my production server.
>
> But when I read your mails, I'm not feeling happy.
> I think it's a kink of luck/voodoo/whatever.
>
> What you must do, I think, is to compile the sieve script with the
> exact version running afterwards.
> And I think you should the remove the compiled .svbin files
> before recreating them again. Don't overwrite them with the compiler.
>
> I think I'll also dig into this any further today.
Please do. I cannot reproduce this so far.

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

Regards,

Stephan.