Sieve settings being ignored since 3.4 update

[Eric B Munson]

Yes, it is clear that the individual rules are enabled, and toggling the 
set was the first thing I tried after searching for this problem.  I am 
sure that roundcube has the set and the individual rules enabled.

I noticed an interesting entry in my syslog that might be relevant:

Jun  8 11:05:14 mail lmtpunix[17357]: sieve runtime error for 
user at domain.net id <5575B061.6060603 at kernel.dk>: Include can not load 
script

There is nothing else in the logs that looks like it is sieve related.

Eric

On 2015-06-09 05:53, Stefan Froehlich wrote:
> Just to clarify:
> You are 100% sure that both the filter is enabled  AND  the filter set
> is enabled?
> 
> Regards,
> Stefan
> 
> On 8/06/2015 11:31 PM, Eric B Munson wrote:
>> I am running Kolab on a debian wheezy install.  I finally updated to 
>> 3.4 recently and since the update my sieve filters are being ignored.  
>> I have ensured that they are marked active in roundcube but all mail 
>> is still ending up in my inbox. I have
>> 
>> $config['managesieve_debug'] = true;
>> 
>> set in my managesieve.inc.php config file but I cannot seem to find 
>> any logs at all.  The sieve log file exists in /var/log/roundcubemail 
>> but it has been 0 bytes since the update.
>> 
>> I keep my config files in a git repo, but the changes required from 
>> 3.3->3.4 were significant and I haven't found anything that looks 
>> obviously wrong in that diff yet.  Has anyone seen this before?
>> 
>> Thanks,
>> Eric
>> _______________________________________________
>> users mailing list
>> users at lists.kolab.org
>> https://lists.kolab.org/mailman/listinfo/users
> 
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users