Why no sieve support (Vacation, Forwarding) in SOGo Groupware

The situation:

If you chose to install both Roundcube webmail and SOGo Groupware during iRedMail installation, sieve support is enabled in only Roundcube webmail.
If you chose to install SOGo Groupware and no Roundcube, sieve support is enabled out of box.

The syntax/format of sieve rules generated by them is not compatible with each other, so iRedMail enables sieve support in Roundcube webmail and disables it in SOGo.

If you want to enable sieve support in SOGo, please enable parameters below (by removing the comment mark // at the beginning of lines below) in SOGo config file (/etc/sogo/sogo.conf):

    SOGoSieveServer = sieve://127.0.0.1:4190/?tls=YES;
    SOGoSieveScriptsEnabled = YES;
    SOGoVacationEnabled = YES;
    SOGoForwardEnabled = YES;

Pitfalls you should know

On SOGo web UI, the sieve rules are read from its SQL database directly, not get from managesieve server. So if you modify the sieve rules by editing the sieve file on file system manually, you will lose the modification next time you update sieve rules from SOGo web UI.
SOGo stores sieve rules in its SQL database first, then dump the rules to mail server (by managesieve service listening on 127.0.0.1:4190).

To disable sieve support in Roundcube, you can simply remove plugin name managesieve from its config parameter $config['plugins'] =.