elmau
/
iredmail-doc
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed: not mention sogo v4 -> v5 change.

This commit is contained in:
Zhang Huangbin 2020-10-28 23:39:47 +08:00
parent 6585b9ffe2
commit 2fe6a2caa0
2 changed files with 35 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
en_US/upgrade/0-upgrade.iredmail.1.3.1-1.3.2.md
View File

@ -24,6 +24,24 @@ so that you can know which version of iRedMail you're running. For example:
1.3.2
```
### SOGo: yum and apt repositories for SOGo v4 has been removed permanently by upstream
SOGo team removed nightly builds for SOGo v4 + v3 permanently (FYI: <https://sogo.nu/bugs/view.php?id=5157>), __ALL__ servers must update yum/apt repository files and switch to SOGo v5. Upgrading is simple, no SQL structure changes from v4 to v5.
- On CentOS, please update file `/etc/yum.repos.d/sogo.repo`, replace version number `4` by `5`, then run:
```
yum clean metadata
yum update
```
- On Debian/Ubuntu, please update file `/etc/apt/sources.list.d/sogo.list` (or `sogo-nightly.list`), replace version number `4` by `5`, then run:
```
apt-get update
apt-get upgrade
```
### Upgrade iRedAPD (Postfix policy server) to the latest stable release (4.6)
!!! attention

17
html/upgrade.iredmail.1.3.1-1.3.2.html
View File

@ -22,6 +22,7 @@
<li><a href="#changelog">ChangeLog</a></li>
<li><a href="#general-all-backends-should-apply-these-changes">General (All backends should apply these changes)</a><ul>
<li><a href="#update-etciredmail-release-with-new-iredmail-version-number">Update /etc/iredmail-release with new iRedMail version number</a></li>
<li><a href="#sogo-yum-and-apt-repositories-for-sogo-v4-has-been-removed-permanently-by-upstream">SOGo: yum and apt repositories for SOGo v4 has been removed permanently by upstream</a></li>
<li><a href="#upgrade-iredapd-postfix-policy-server-to-the-latest-stable-release-46">Upgrade iRedAPD (Postfix policy server) to the latest stable release (4.6)</a></li>
<li><a href="#upgrade-mlmmjadmin-to-the-latest-stable-release-304">Upgrade mlmmjadmin to the latest stable release (3.0.4)</a></li>
<li><a href="#upgrade-iredadmin-open-source-edition-to-the-latest-stable-release-11">Upgrade iRedAdmin (open source edition) to the latest stable release (1.1)</a></li>
@ -61,6 +62,22 @@ so that you can know which version of iRedMail you're running. For example:</p>
<pre><code>1.3.2
</code></pre>
<h3 id="sogo-yum-and-apt-repositories-for-sogo-v4-has-been-removed-permanently-by-upstream">SOGo: yum and apt repositories for SOGo v4 has been removed permanently by upstream</h3>
<p>SOGo team removed nightly builds for SOGo v4 + v3 permanently (FYI: <a href="https://sogo.nu/bugs/view.php?id=5157">https://sogo.nu/bugs/view.php?id=5157</a>), <strong>ALL</strong> servers must update yum/apt repository files and switch to SOGo v5. Upgrading is simple, no SQL structure changes from v4 to v5.</p>
<ul>
<li>On CentOS, please update file <code>/etc/yum.repos.d/sogo.repo</code>, replace version number <code>4</code> by <code>5</code>, then run:</li>
</ul>
<pre><code>yum clean metadata
yum update
</code></pre>
<ul>
<li>On Debian/Ubuntu, please update file <code>/etc/apt/sources.list.d/sogo.list</code> (or <code>sogo-nightly.list</code>), replace version number <code>4</code> by <code>5</code>, then run:</li>
</ul>
<pre><code>apt-get update
apt-get upgrade
</code></pre>
<h3 id="upgrade-iredapd-postfix-policy-server-to-the-latest-stable-release-46">Upgrade iRedAPD (Postfix policy server) to the latest stable release (4.6)</h3>
<div class="admonition attention">
<p class="admonition-title">Attention</p>