In 0001819 sogo changed his behaviour regarding sieve rules parsing.
This caused a problem in our organization, where a system manager prepares and mantains sieve rules for users (enabling SOGoSieveScriptsEnabled on a temporary basis). Most of the time he set SOGoSieveScriptsEnabled to no, avoiding the modification of rules directly by the users.
After 0001819 this seems no longer possible, beacause with SOGoSieveScriptsEnabled set to no, there is no more sieve rules parsing.
Do you have a workaround or a suggestion for our scenario? Thank you -- users@sogo.nu https://inverse.ca/sogo/lists
