Mention how to disable Cluebringer integration in iRedAdmin-Pro.

This commit is contained in:
Zhang Huangbin 2015-12-14 22:24:20 +08:00
parent e1bab830c6
commit a3f187d4ca
4 changed files with 21 additions and 4 deletions

View File

@ -76,6 +76,8 @@ That's it.
### After migration
#### Disable Cluebringer in Postfix
After migrated to iRedAPD, we need to update Postfix config file
`/etc/postfix/main.cf` (Linux) or `/usr/local/etc/postfix/main.cf` (FreeBSD)
to remove Cluebringer settings:
@ -123,3 +125,9 @@ smtpd_end_of_data_restrictions =
```
* Optionally, you can drop its SQL database `cluebringer` also.
#### Disable Cluebringer in iRedAdmin-Pro
To disable Cluebringer integration in iRedAdmin-Pro, please set
`policyd_enabled = False` in iRedAdmin-Pro config file, then restart Apache
or uwsgi (if you're running Nginx) service.

View File

@ -66,7 +66,7 @@ In iRedMail-0.9.2 and earlier releases, Amavisd was incorrectly configured
which causes it treats external sender as internal user, and it (incorrectly)
signs DKIM on inbound message. This is wrong. Please follow steps below to fix it.
With below changes, Amavisd will aply policy bank 'ORIGINATING' to emails
With below changes, Amavisd will apply policy bank 'ORIGINATING' to emails
submitted through submission (port 587) by smtp authenticated user. This way
we clearly separate emails submitted by authenticated users and inbound message
sent by others, and Amavisd won't sign DKIM on inbound message anymore.

View File

@ -18,7 +18,11 @@
<li><a href="#migrate-to-iredapd">Migrate to iRedAPD</a><ul>
<li><a href="#upgrade-iredapd-to-170-or-later-releases">Upgrade iRedAPD to 1.7.0 or later releases</a></li>
<li><a href="#migrate-cluebringer-to-iredapd">Migrate Cluebringer to iRedAPD</a></li>
<li><a href="#after-migration">After migration</a></li>
<li><a href="#after-migration">After migration</a><ul>
<li><a href="#disable-cluebringer-in-postfix">Disable Cluebringer in Postfix</a></li>
<li><a href="#disable-cluebringer-in-iredadmin-pro">Disable Cluebringer in iRedAdmin-Pro</a></li>
</ul>
</li>
</ul>
</li>
</ul>
@ -86,6 +90,7 @@ cluebringer_db_password = ''
<p>That's it.</p>
<h3 id="after-migration">After migration</h3>
<h4 id="disable-cluebringer-in-postfix">Disable Cluebringer in Postfix</h4>
<p>After migrated to iRedAPD, we need to update Postfix config file
<code>/etc/postfix/main.cf</code> (Linux) or <code>/usr/local/etc/postfix/main.cf</code> (FreeBSD)
to remove Cluebringer settings:</p>
@ -140,7 +145,11 @@ smtpd_end_of_data_restrictions =
<ul>
<li>Optionally, you can drop its SQL database <code>cluebringer</code> also.</li>
</ul><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. If you found something wrong, please do <a href="http://www.iredmail.org/contact.html">contact us</a> to fix it.<script>
</ul>
<h4 id="disable-cluebringer-in-iredadmin-pro">Disable Cluebringer in iRedAdmin-Pro</h4>
<p>To disable Cluebringer integration in iRedAdmin-Pro, please set
<code>policyd_enabled = False</code> in iRedAdmin-Pro config file, then restart Apache
or uwsgi (if you're running Nginx) service.</p><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. If you found something wrong, please do <a href="http://www.iredmail.org/contact.html">contact us</a> to fix it.<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)

View File

@ -113,7 +113,7 @@ latest stable release immediately: <a href="http://trac.roundcube.net/wiki/Howto
<p>In iRedMail-0.9.2 and earlier releases, Amavisd was incorrectly configured
which causes it treats external sender as internal user, and it (incorrectly)
signs DKIM on inbound message. This is wrong. Please follow steps below to fix it.</p>
<p>With below changes, Amavisd will aply policy bank 'ORIGINATING' to emails
<p>With below changes, Amavisd will apply policy bank 'ORIGINATING' to emails
submitted through submission (port 587) by smtp authenticated user. This way
we clearly separate emails submitted by authenticated users and inbound message
sent by others, and Amavisd won't sign DKIM on inbound message anymore.</p>