Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hello, just for information, the update to version 3.0.6 did not fix the problem for me, I'm still having the same issue. I had to apply my workaround (create symbolic links) to make it work again. Regards, Ralf Am 02.03.2018 um 20:11 schrieb rfk: Hi Ken, my distribution is Gentoo and

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hi Ken, my distribution is Gentoo and my previous cyrus version was 2.5.10. Then I upgraded to 3.0.4 but this ebuild (though marked stable by the Gentoo devs) was terminating "abnormally" all the time. Finally I upgraded to 3.0.5 which is running fine until now - well, except for sieve.

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hi Sebastian, in my second post you can see my cyrus.conf: https://lists.andrew.cmu.edu/pipermail/info-cyrus/2018-February/039985.html No "-C" flags in use though. Regards, Ralf Am 02.03.2018 um 09:21 schrieb Sebastian Hagedorn: Hi Ralf, thanks a lot for your feedback, seems like we're

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

I've done some investigating this morning and it appears that you are correct in that lmtpd and timsieved differ in how they handle the hierarchy separator.  But I'm not sure just yet when this split happened. Did you upgrade from 3.0.4 or from 2.x? On 03/01/2018 03:36 PM, rfk wrote: Hey

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hi Ralf, thanks a lot for your feedback, seems like we're coming closer. Although I'm not sure what port 24 is supposed to be in your swaks command I just sent myself an e-mail while strace was attached to cyrusmaster. The log revealed the following:

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hey Sebastian, thanks a lot for your feedback, seems like we're coming closer. Although I'm not sure what port 24 is supposed to be in your swaks command I just sent myself an e-mail while strace was attached to cyrusmaster. The log revealed the following:

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Not really. My best suggestion would be to strace the lmtp process to see if the sieve scripts are even found and opened. On a test system I did it like this: strace -f -ff -o /tmp/lmtptrace -p It might be better to prefork an lmtpd and to specifically strace that pid, but in my case it

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hello, still no other ideas? Ralf Am 15.02.2018 um 19:37 schrieb rfk: Hi, I'm so sorry, don't know how this could happen, but the last line of my configuration was lost during copy and paste: altnamespace: 0 So it is already disabled. Ralf Am 15.02.2018 um 19:32 schrieb Michael

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hi, I'm so sorry, don't know how this could happen, but the last line of my configuration was lost during copy and paste: altnamespace: 0 So it is already disabled. Ralf Am 15.02.2018 um 19:32 schrieb Michael Menge: Hi, Quoting rfk : Hi, thanks for your

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hi, thanks for your feedback. Unfortunately sievec reports nothing: # grep -v ^# roundcube.script require ["imapflags","fileinto"]; if anyof (header :contains "Subject" "test") { setflag "\\Seen"; fileinto "INBOX/Trash"; stop; } # sievec roundcube.script test #

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hi, Does the "sievec" compiler report any errors if you try to compile your sieve scripts by hand? Its manpage is here: https://www.cyrusimap.org/imap/reference/manpages/systemcommands/sievec.html Cheers, ellie On Thu, Feb 15, 2018, at 5:28 AM, rfk wrote: > Hello, > > recently I updated my

Sieve stopped working after updating cyrus-imapd to 3.0.5

Hello, recently I updated my cyrus-imapd installation from verion 2.5.10 to version 3.0.5. Unfortunately the sieve filters stopped working since then. The rest is working fine. The filters are listed in the sieveshell and all incoming mails get tagged with "X-Sieve: CMU Sieve 3.0". However