[ingo] Sieve scripts not getting activated on save?

Darrell Budic budic at onholyground.com
Wed Aug 3 16:35:56 UTC 2011

On Jul 28, 2011, at 2:49 AM, Jan Schneider wrote:

> Zitat von Darrell Budic <budic at onholyground.com>:
>> Did something change in the last ingo update? I had thought that sieve scripts would upload and activate when you make changes like saving a new vacation script, but in the latest update (2.0.3, using sieve against a cyrus backend) this doesn't seem to happen. You can go into the script and compare the currently active to the currently script, and activate it from there. I don't want to have to train users to do this though. Did I just miss a preference or setting someplace to have this happen automatically?
> It's a preference, but it has always been one, and it seems to still work fine here.
> Jan.

Yeah, that's what I thought. I think I have some messed up permissions for Ingo somewhere, but I'm not finding it and not sure where to look. Is this an Administrative setting for Ingo or a User Preference for Ingo?


More information about the ingo mailing list