Re: sieve not working after migration to 16.1

Thank you very much,

the problem is solved now.

The short answer is:
After some debugging without any reasonable results I found that the 
complete _filter-set_ in roundcube was disabled. Individual scripts were 
enabled, but the corresponding filter set named "roundcube" was grey and 
thus disabled. I feel a little bit stupid about this, but I really did 
not know that one could enable and disable complete filter sets at all 
and I still don't know _why_ it has been disabled because it was working 
before the migration to 16.1.

But one interesting thing still remains: While debugging this problem I 
tried the sieveshell on the kolab server and always got this result:

[root@kolab ~]# sieveshell localhost
connecting to localhost
unable to connect to server at /usr/bin/sieveshell line 190.

Any idea whats wrong here, or is this expected behaviour and maybe I'm 
again beeing stupid?!

Cheers
Thomas

On 17.08.2020 07:14, hede wrote:
> On Sun, 16 Aug 2020 21:53:33 +0200 "Reitelbach, Thomas"
> <[email protected]> wrote:
> 
>> Sorry, I have no idea where to look for the reason and where to 
>> activate
>> debugging-logs?!
>> Can someone point me to the right direction for debugging?
> 
> debugging can be enabled in imapd.conf via "debug: 1"
> 
> But maybe you can try some other things first. For example check if
> sievedir is correctly set in imapd.conf. Or you can experiment with
> the sieveshell (a shell command on the kolab server), log in as a user
> and check if "list" does list the current sieve script and what
> happens if you "activate" the script there.
> 
> regards
> hede