The problem is not only that it saves the sieve script but actives it!

This way the wrong sieve script may be activated even if you only edit and save another setting which doesn't refer to sieve.

When the user has multiple Sieve scripts, SOGo should allow the user to select the script to activate.

For example, see SmartSieve :

http://smartsieve.sourceforge.net/images/scripts.png

sogo should not save/or/activate the sieve script if the user didn't modify its settings...

there are 2 possibilities:
1) (the best) admin can include sieve command for all users.

2) or, when you close settings window, sogo save sieve script if (and only if) you modified something in.

It's now possible in v1.3.8. Use sogo-tool user-preferences set ...

This will update, if required, Sieve scripts and SOGo's metadata.

Never toy around with Sieve scripts behind SOGo's back.