New: why.no.sieve.support.in.sogo.html.
This commit is contained in:
parent
dee52cb680
commit
d30a5d5e08
|
@ -0,0 +1,35 @@
|
|||
# Why no Sieve (Vacation, Forwarding) support 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;
|
||||
```
|
||||
|
||||
!!! 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`).
|
||||
|
||||
To disable sieve support in Roundcube, you can simply remove plugin name
|
||||
`managesieve` from its config parameter `$config['plugins'] =`.
|
|
@ -222,6 +222,7 @@
|
|||
<li><a href="backup.restore.html">Backup and restore</a></li>
|
||||
<li><a href="customize.maildir.path.html">Customize maildir path</a></li>
|
||||
<li><a href="file.locations.html">Locations of configuration and log files of major components</a></li>
|
||||
<li><a href="why.no.sieve.support.in.sogo.html">Why no Sieve (Vacation, Forwarding) support in SOGo Groupware</a></li>
|
||||
</ul><div class="footer">
|
||||
<p style="text-align: center; color: grey;">All documents are available in <a href="https://bitbucket.org/zhb/iredmail-docs/src">BitBucket repository</a>, and published under <a href="http://creativecommons.org/licenses/by-nd/3.0/us/" target="_blank">Creative Commons</a> license. You can <a href="https://bitbucket.org/zhb/iredmail-docs/get/tip.tar.bz2">download the latest version</a> for offline reading. If you found something wrong, please do <a href="https://www.iredmail.org/contact.html">contact us</a> to fix it.</p>
|
||||
</div>
|
||||
|
|
|
@ -0,0 +1,62 @@
|
|||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||||
<title>Why no Sieve (Vacation, Forwarding) support in SOGo Groupware</title>
|
||||
<link rel="stylesheet" type="text/css" href="./css/markdown.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="navigation">
|
||||
<a href="https://www.iredmail.org" target="_blank">
|
||||
<img alt="iRedMail web site"
|
||||
src="./images/logo-iredmail.png"
|
||||
style="vertical-align: middle; height: 30px;"
|
||||
/>
|
||||
<span>iRedMail</span>
|
||||
</a>
|
||||
// <a href="./index.html">Document Index</a></div><h1 id="why-no-sieve-vacation-forwarding-support-in-sogo-groupware">Why no Sieve (Vacation, Forwarding) support in SOGo Groupware</h1>
|
||||
<p>The situation:</p>
|
||||
<ul>
|
||||
<li>If you chose to install both Roundcube webmail and SOGo Groupware during
|
||||
iRedMail installation, sieve support is enabled in only Roundcube webmail.</li>
|
||||
<li>If you chose to install SOGo Groupware and no Roundcube, sieve support
|
||||
is enabled out of box.</li>
|
||||
</ul>
|
||||
<p>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.</p>
|
||||
<p>If you want to enable sieve support in SOGo, please enable parameters below
|
||||
(by removing the comment mark <code>//</code> at the beginning of lines below) in SOGo
|
||||
config file (<code>/etc/sogo/sogo.conf</code>):</p>
|
||||
<pre><code> SOGoSieveServer = sieve://127.0.0.1:4190/?tls=YES;
|
||||
SOGoSieveScriptsEnabled = YES;
|
||||
SOGoVacationEnabled = YES;
|
||||
SOGoForwardEnabled = YES;
|
||||
</code></pre>
|
||||
|
||||
<div class="admonition warning">
|
||||
<p class="admonition-title">Pitfalls you should know</p>
|
||||
<ul>
|
||||
<li>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.</li>
|
||||
<li>SOGo stores sieve rules in its SQL database first, then dump the rules to
|
||||
mail server (by managesieve service listening on <code>127.0.0.1:4190</code>).</li>
|
||||
</ul>
|
||||
</div>
|
||||
<p>To disable sieve support in Roundcube, you can simply remove plugin name
|
||||
<code>managesieve</code> from its config parameter <code>$config['plugins'] =</code>.</p><div class="footer">
|
||||
<p style="text-align: center; color: grey;">All documents are available in <a href="https://bitbucket.org/zhb/iredmail-docs/src">BitBucket repository</a>, and published under <a href="http://creativecommons.org/licenses/by-nd/3.0/us/" target="_blank">Creative Commons</a> license. You can <a href="https://bitbucket.org/zhb/iredmail-docs/get/tip.tar.bz2">download the latest version</a> for offline reading. If you found something wrong, please do <a href="https://www.iredmail.org/contact.html">contact us</a> to fix it.</p>
|
||||
</div>
|
||||
<!-- Global site tag (gtag.js) - Google Analytics -->
|
||||
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-3293801-21"></script>
|
||||
<script>
|
||||
window.dataLayer = window.dataLayer || [];
|
||||
function gtag(){dataLayer.push(arguments);}
|
||||
gtag('js', new Date());
|
||||
|
||||
gtag('config', 'UA-3293801-21');
|
||||
</script>
|
||||
</body></html>
|
Loading…
Reference in New Issue