2018-03-13 04:21:41 -06:00
|
|
|
# Why no sieve support (Vacation, Forwarding) in SOGo Groupware
|
2018-03-13 04:19:32 -06:00
|
|
|
|
2021-07-17 05:22:24 -05:00
|
|
|
The situations:
|
2018-03-13 04:19:32 -06:00
|
|
|
|
|
|
|
|
* 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
|
2021-07-17 05:22:24 -05:00
|
|
|
is enabled in SOGo out of box.
|
2018-03-13 04:19:32 -06:00
|
|
|
|
2021-07-17 05:22:24 -05:00
|
|
|
The syntax/format of sieve rules generated by them are not compatible
|
2018-03-13 04:19:32 -06:00
|
|
|
with each other, so iRedMail enables sieve support in Roundcube webmail and
|
|
|
|
|
disables it in SOGo.
|
|
|
|
|
|
2021-07-17 05:22:24 -05:00
|
|
|
!!! warning "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`).
|
|
|
|
|
|
2018-03-13 04:19:32 -06:00
|
|
|
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;
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
To disable sieve support in Roundcube, you can simply remove plugin name
|
|
|
|
|
`managesieve` from its config parameter `$config['plugins'] =`.
|
