Sync iRedMail upgrade tutorials.
This commit is contained in:
Zhang Huangbin
parent
6c4e652036
commit
ce09680b03
|
|
@ -41,8 +41,7 @@ latest stable release:
|
|||
### Upgrade Roundcube webmail to the latest stable release (1.3.0)
|
||||
|
||||
!!! warning "Roundcube 1.3"
|
||||
|
||||
|
||||
|
||||
* Roundcube 1.3 requires at least __PHP 5.4__. If your server is still running
|
||||
PHP 5.3 and cannot upgrade to 5.4, please upgrade Roundcube to the latest
|
||||
1.2 branch (1.2.5) instead.
|
||||
|
|
|
|||
|
|
@ -10,6 +10,8 @@
|
|||
|
||||
## ChangeLog
|
||||
|
||||
* Mar 4, Upgrade SOGo from v3 to v4.
|
||||
* Mar 4, Upgrade Roundcube webmail to the latet version - 1.3.5.
|
||||
* Mar 1, SQL structure changes in `vmail` database.
|
||||
* Feb 14, 2018: [SECURITY] Fixed: Nginx snippet file doesn't block access to Roundcube sensitive files.
|
||||
* Feb 11, 2018: netdata integration.
|
||||
|
|
@ -42,6 +44,45 @@ so that you can know which version of iRedMail you're running. For example:
|
|||
Please follow below tutorial to upgrade iRedAPD to the latest stable release:
|
||||
[Upgrade iRedAPD to the latest stable release](./upgrade.iredapd.html)
|
||||
|
||||
### Upgrade iRedAdmin (open source edition) to the latest stable release (0.9)
|
||||
|
||||
Please follow this tutorial to upgrade iRedAdmin open source edition to the
|
||||
latest stable release:
|
||||
[Upgrade iRedAdmin to the latest stable release](./migrate.or.upgrade.iredadmin.html)
|
||||
|
||||
### Upgrade Roundcube webmail to the latest stable release (1.3.5)
|
||||
|
||||
!!! warning "Roundcube 1.3"
|
||||
|
||||
* Roundcube 1.3 requires at least __PHP 5.4__. If your server is still running
|
||||
PHP 5.3 and cannot upgrade to 5.4, please upgrade Roundcube to the latest
|
||||
1.2 branch (1.2.5) instead.
|
||||
* Roundcube 1.3 no longer supports IE < 10 and old versions of Firefox,
|
||||
Chrome and Safari.
|
||||
* Roundcube 1.3 uses jQuery 3.2 and will not work with current jQuery
|
||||
mobile plugin. If you use any third-party plugin, please check its
|
||||
website to make sure it's compatible with Roundcube 1.3 before upgrading.
|
||||
|
||||
With the release of Roundcube 1.3.0, the previous stable release branches
|
||||
1.2.x and 1.1.x will switch in to LTS low maintenance mode which means
|
||||
they will only receive important security updates but no longer any regular
|
||||
improvement updates.
|
||||
|
||||
Please follow Roundcube official tutorial to upgrade Roundcube webmail to the
|
||||
latest stable release immediately:
|
||||
|
||||
* [How to upgrade Roundcube](https://github.com/roundcube/roundcubemail/wiki/Upgrade).
|
||||
|
||||
### Upgrade SOGo from v3 to v4
|
||||
|
||||
SOGo v4 was released on Mar 7, 2018 by the SOGo team (<https://sogo.nu>), it
|
||||
will become the main branch with most active development.
|
||||
|
||||
If you're satisfied with SOGo v3, you're free to continue running v3. but if
|
||||
you want to try v4, please follow our tutorial below to upgrade it.
|
||||
|
||||
* [Upgrade SOGo from v3 to v4](./upgrade.sogo.3.to.4.html)
|
||||
|
||||
### Fixed: SOGo backup script contains 3 issues
|
||||
|
||||
SOGo backup script `/var/vmail/backup/backup_sogo.sh` shipped in iRedMail-0.9.7
|
||||
|
|
@ -267,18 +308,18 @@ postscreen_dnsbl_sites =
|
|||
|
||||
Reloading or restarting Postfix is required.
|
||||
|
||||
### OpenBSD: Upgrade uwsgi to the latest 2.0.16
|
||||
### OpenBSD: Upgrade uwsgi to the latest 2.0.17
|
||||
|
||||
uwsgi is the interface between Nginx and iRedAdmin, so if you're running
|
||||
iRedAdmin, it's recommended to upgrade uwsgi to the latest version, 2.0.16.
|
||||
iRedAdmin, it's recommended to upgrade uwsgi to the latest version, 2.0.17.
|
||||
|
||||
Steps: Download the latest uwsgi, compile it, then restart uwsgi service.
|
||||
|
||||
```
|
||||
cd /root/
|
||||
ftp https://projects.unbit.it/downloads/uwsgi-2.0.16.tar.gz
|
||||
tar zxf uwsgi-2.0.16.tar.gz
|
||||
cd uwsgi-2.0.16
|
||||
ftp https://projects.unbit.it/downloads/uwsgi-2.0.17.tar.gz
|
||||
tar zxf uwsgi-2.0.17.tar.gz
|
||||
cd uwsgi-2.0.17
|
||||
python setup.py install
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,122 @@
|
|||
# Upgrade SOGo from v3 to v4
|
||||
|
||||
[TOC]
|
||||
|
||||
SOGo v4 was released on Mar 7, 2018 by the SOGo team (<https://sogo.nu>), it
|
||||
will become the main branch with most active development.
|
||||
If you're satisfied with SOGo v3, you're free to stick to it.
|
||||
|
||||
## Upgrade SOGo On RHEL/CentOS
|
||||
|
||||
* Backup config files first:
|
||||
|
||||
```
|
||||
mkdir -p /root/sogo-backup/{sogo,sysconfig}
|
||||
cp /etc/sogo/* /root/sogo-backup/sogo/
|
||||
cp /etc/sysconfig/sogo /root/sogo-backup/sysconfig/
|
||||
```
|
||||
|
||||
* Backup its SQL database:
|
||||
|
||||
```
|
||||
bash /var/vmail/backup/backup_sogo.sh
|
||||
```
|
||||
|
||||
* Open file `/etc/yum.repos.d/sogo.repo`, change the version number in
|
||||
`baseurl=` line from `3` to `4`:
|
||||
|
||||
```
|
||||
baseurl=https://packages.inverse.ca/SOGo/nightly/4/rhel/$releasever/$basearch/
|
||||
```
|
||||
|
||||
* Upgrade SOGo packages:
|
||||
|
||||
```
|
||||
yum clean all
|
||||
yum update sogo* sope*
|
||||
```
|
||||
|
||||
* Run the script shipped in SOGo-4.x to update SQL structure:
|
||||
* For LDAP and MySQL/MariaDB backends:
|
||||
|
||||
```
|
||||
bash /usr/share/doc/sogo-4.*/sql-update-3.2.10_to_4.0.0-mysql.sh
|
||||
```
|
||||
|
||||
* For PostgreSQL backend:
|
||||
|
||||
```bash /usr/share/doc/sogo-4.*/sql-update-3.2.10_to_4.0.0.sh```
|
||||
|
||||
* Restart SOGo service:
|
||||
|
||||
```
|
||||
service sogod restart
|
||||
```
|
||||
|
||||
## Upgrade SOGo On Debian/Ubuntu
|
||||
|
||||
* Backup config files first:
|
||||
|
||||
```
|
||||
mkdir -p /root/sogo-backup/{sogo,default}
|
||||
cp /etc/sogo/* /root/sogo-backup/sogo/
|
||||
cp /etc/default/sogo /root/sogo-backup/default/
|
||||
```
|
||||
|
||||
* Backup its SQL database:
|
||||
|
||||
```
|
||||
bash /var/vmail/backup/backup_sogo.sh
|
||||
```
|
||||
|
||||
* Open file `/etc/apt/sources.list`, change the version number `3` to `4`, like
|
||||
below:
|
||||
|
||||
```
|
||||
# Debian
|
||||
https://packages.inverse.ca/SOGo/nightly/4/debian ...
|
||||
|
||||
# Ubuntu
|
||||
https://packages.inverse.ca/SOGo/nightly/4/ubuntu ...
|
||||
```
|
||||
|
||||
* Upgrade SOGo packages:
|
||||
|
||||
```
|
||||
apt-get update
|
||||
apt-get install --only-upgrade sogo sogo-activesync
|
||||
```
|
||||
|
||||
* Run the script shipped in SOGo-4.x to update SQL structure:
|
||||
* For LDAP and MySQL/MariaDB backends:
|
||||
|
||||
```
|
||||
bash /usr/share/doc/sogo/sql-update-3.2.10_to_4.0.0-mysql.sh
|
||||
```
|
||||
|
||||
* For PostgreSQL backend:
|
||||
|
||||
```bash /usr/share/doc/sogo/sql-update-3.2.10_to_4.0.0.sh```
|
||||
|
||||
* Restart SOGo service:
|
||||
|
||||
```
|
||||
service sogo restart
|
||||
```
|
||||
|
||||
## Upgrade SOGo On FreeBSD
|
||||
|
||||
FreeBSD ports tree still ships SOGo-3, so no SQL structure change after you
|
||||
update ports `www/sogo3` and `www/sogo3-activesync`.
|
||||
|
||||
## Upgrade SOGo On OpenBSD
|
||||
|
||||
OpenBSD 6.3 still ships SOGo-3, so no SQL structure change after you update
|
||||
sogo/sope packages with `pkg_add` command.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
If SOGo doesn't work as expected, please check its log file
|
||||
`/var/log/sogo/sogo.log`. If you don't understand what the error message means,
|
||||
please extract related error message and post to our online support forum:
|
||||
<https://forum.iredmail.org/>.
|
||||
|
|
@ -23,12 +23,15 @@
|
|||
<li><a href="#general-all-backends-should-apply-these-steps">General (All backends should apply these steps)</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="#upgrade-iredapd-postfix-policy-server-to-the-latest-stable-release-22">Upgrade iRedAPD (Postfix policy server) to the latest stable release (2.2)</a></li>
|
||||
<li><a href="#upgrade-iredadmin-open-source-edition-to-the-latest-stable-release-09">Upgrade iRedAdmin (open source edition) to the latest stable release (0.9)</a></li>
|
||||
<li><a href="#upgrade-roundcube-webmail-to-the-latest-stable-release-135">Upgrade Roundcube webmail to the latest stable release (1.3.5)</a></li>
|
||||
<li><a href="#upgrade-sogo-from-v3-to-v4">Upgrade SOGo from v3 to v4</a></li>
|
||||
<li><a href="#fixed-sogo-backup-script-contains-3-issues">Fixed: SOGo backup script contains 3 issues</a></li>
|
||||
<li><a href="#fail2ban-new-jail-postfix-pregreet">Fail2ban: new jail postfix-pregreet</a></li>
|
||||
<li><a href="#fixed-nginx-snippet-file-hard-codes-static-file-types-for-iredadmin">Fixed: Nginx snippet file hard-codes static file types for iRedAdmin</a></li>
|
||||
<li><a href="#security-fixed-nginx-snippet-file-doesnt-block-access-to-roundcube-sensitive-files">[SECURITY] Fixed: Nginx snippet file doesn't block access to Roundcube sensitive files</a></li>
|
||||
<li><a href="#fix-unexpected-dnsbl-query-result-for-site-bbarracudacentralorg">Fix unexpected DNSBL query result for site b.barracudacentral.org</a></li>
|
||||
<li><a href="#openbsd-upgrade-uwsgi-to-the-latest-2016">OpenBSD: Upgrade uwsgi to the latest 2.0.16</a></li>
|
||||
<li><a href="#openbsd-upgrade-uwsgi-to-the-latest-2017">OpenBSD: Upgrade uwsgi to the latest 2.0.17</a></li>
|
||||
<li><a href="#optional-log-mail-subject-sender-size-in-mail-deliver-log">[OPTIONAL] Log mail subject, sender, size in mail deliver log</a></li>
|
||||
<li><a href="#optional-integrate-netdata-fancy-system-monitor">[OPTIONAL] integrate netdata - fancy system monitor</a></li>
|
||||
</ul>
|
||||
|
|
@ -67,6 +70,8 @@ check <a href="https://www.iredmail.org/support.html">the details</a> and
|
|||
</div>
|
||||
<h2 id="changelog">ChangeLog</h2>
|
||||
<ul>
|
||||
<li>Mar 4, Upgrade SOGo from v3 to v4.</li>
|
||||
<li>Mar 4, Upgrade Roundcube webmail to the latet version - 1.3.5.</li>
|
||||
<li>Mar 1, SQL structure changes in <code>vmail</code> database.</li>
|
||||
<li>Feb 14, 2018: [SECURITY] Fixed: Nginx snippet file doesn't block access to Roundcube sensitive files.</li>
|
||||
<li>Feb 11, 2018: netdata integration.</li>
|
||||
|
|
@ -93,6 +98,41 @@ so that you can know which version of iRedMail you're running. For example:</p>
|
|||
<h3 id="upgrade-iredapd-postfix-policy-server-to-the-latest-stable-release-22">Upgrade iRedAPD (Postfix policy server) to the latest stable release (2.2)</h3>
|
||||
<p>Please follow below tutorial to upgrade iRedAPD to the latest stable release:
|
||||
<a href="./upgrade.iredapd.html">Upgrade iRedAPD to the latest stable release</a></p>
|
||||
<h3 id="upgrade-iredadmin-open-source-edition-to-the-latest-stable-release-09">Upgrade iRedAdmin (open source edition) to the latest stable release (0.9)</h3>
|
||||
<p>Please follow this tutorial to upgrade iRedAdmin open source edition to the
|
||||
latest stable release:
|
||||
<a href="./migrate.or.upgrade.iredadmin.html">Upgrade iRedAdmin to the latest stable release</a></p>
|
||||
<h3 id="upgrade-roundcube-webmail-to-the-latest-stable-release-135">Upgrade Roundcube webmail to the latest stable release (1.3.5)</h3>
|
||||
<div class="admonition warning">
|
||||
<p class="admonition-title">Roundcube 1.3</p>
|
||||
<ul>
|
||||
<li>Roundcube 1.3 requires at least <strong>PHP 5.4</strong>. If your server is still running
|
||||
PHP 5.3 and cannot upgrade to 5.4, please upgrade Roundcube to the latest
|
||||
1.2 branch (1.2.5) instead.</li>
|
||||
<li>Roundcube 1.3 no longer supports IE < 10 and old versions of Firefox,
|
||||
Chrome and Safari.</li>
|
||||
<li>Roundcube 1.3 uses jQuery 3.2 and will not work with current jQuery
|
||||
mobile plugin. If you use any third-party plugin, please check its
|
||||
website to make sure it's compatible with Roundcube 1.3 before upgrading.</li>
|
||||
</ul>
|
||||
<p>With the release of Roundcube 1.3.0, the previous stable release branches
|
||||
1.2.x and 1.1.x will switch in to LTS low maintenance mode which means
|
||||
they will only receive important security updates but no longer any regular
|
||||
improvement updates.</p>
|
||||
</div>
|
||||
<p>Please follow Roundcube official tutorial to upgrade Roundcube webmail to the
|
||||
latest stable release immediately:</p>
|
||||
<ul>
|
||||
<li><a href="https://github.com/roundcube/roundcubemail/wiki/Upgrade">How to upgrade Roundcube</a>.</li>
|
||||
</ul>
|
||||
<h3 id="upgrade-sogo-from-v3-to-v4">Upgrade SOGo from v3 to v4</h3>
|
||||
<p>SOGo v4 was released on Mar 7, 2018 by the SOGo team (<a href="https://sogo.nu">https://sogo.nu</a>), it
|
||||
will become the main branch with most active development.</p>
|
||||
<p>If you're satisfied with SOGo v3, you're free to continue running v3. but if
|
||||
you want to try v4, please follow our tutorial below to upgrade it.</p>
|
||||
<ul>
|
||||
<li><a href="./upgrade.sogo.3.to.4.html">Upgrade SOGo from v3 to v4</a></li>
|
||||
</ul>
|
||||
<h3 id="fixed-sogo-backup-script-contains-3-issues">Fixed: SOGo backup script contains 3 issues</h3>
|
||||
<p>SOGo backup script <code>/var/vmail/backup/backup_sogo.sh</code> shipped in iRedMail-0.9.7
|
||||
and earlier releases contains 3 issues:</p>
|
||||
|
|
@ -290,14 +330,14 @@ a range from <code>127.0.0.2</code> to <code>127.0.0.11</code>), so we should ch
|
|||
</code></pre>
|
||||
|
||||
<p>Reloading or restarting Postfix is required.</p>
|
||||
<h3 id="openbsd-upgrade-uwsgi-to-the-latest-2016">OpenBSD: Upgrade uwsgi to the latest 2.0.16</h3>
|
||||
<h3 id="openbsd-upgrade-uwsgi-to-the-latest-2017">OpenBSD: Upgrade uwsgi to the latest 2.0.17</h3>
|
||||
<p>uwsgi is the interface between Nginx and iRedAdmin, so if you're running
|
||||
iRedAdmin, it's recommended to upgrade uwsgi to the latest version, 2.0.16.</p>
|
||||
iRedAdmin, it's recommended to upgrade uwsgi to the latest version, 2.0.17.</p>
|
||||
<p>Steps: Download the latest uwsgi, compile it, then restart uwsgi service.</p>
|
||||
<pre><code>cd /root/
|
||||
ftp https://projects.unbit.it/downloads/uwsgi-2.0.16.tar.gz
|
||||
tar zxf uwsgi-2.0.16.tar.gz
|
||||
cd uwsgi-2.0.16
|
||||
ftp https://projects.unbit.it/downloads/uwsgi-2.0.17.tar.gz
|
||||
tar zxf uwsgi-2.0.17.tar.gz
|
||||
cd uwsgi-2.0.17
|
||||
python setup.py install
|
||||
</code></pre>
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,156 @@
|
|||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||||
<title>Upgrade SOGo from v3 to v4</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="upgrade-sogo-from-v3-to-v4">Upgrade SOGo from v3 to v4</h1>
|
||||
<div class="toc">
|
||||
<ul>
|
||||
<li><a href="#upgrade-sogo-from-v3-to-v4">Upgrade SOGo from v3 to v4</a><ul>
|
||||
<li><a href="#upgrade-sogo-on-rhelcentos">Upgrade SOGo On RHEL/CentOS</a></li>
|
||||
<li><a href="#upgrade-sogo-on-debianubuntu">Upgrade SOGo On Debian/Ubuntu</a></li>
|
||||
<li><a href="#upgrade-sogo-on-freebsd">Upgrade SOGo On FreeBSD</a></li>
|
||||
<li><a href="#upgrade-sogo-on-openbsd">Upgrade SOGo On OpenBSD</a></li>
|
||||
<li><a href="#troubleshooting">Troubleshooting</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<p>SOGo v4 was released on Mar 7, 2018 by the SOGo team (<a href="https://sogo.nu">https://sogo.nu</a>), it
|
||||
will become the main branch with most active development.
|
||||
If you're satisfied with SOGo v3, you're free to stick to it.</p>
|
||||
<h2 id="upgrade-sogo-on-rhelcentos">Upgrade SOGo On RHEL/CentOS</h2>
|
||||
<ul>
|
||||
<li>Backup config files first:</li>
|
||||
</ul>
|
||||
<pre><code>mkdir -p /root/sogo-backup/{sogo,sysconfig}
|
||||
cp /etc/sogo/* /root/sogo-backup/sogo/
|
||||
cp /etc/sysconfig/sogo /root/sogo-backup/sysconfig/
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>Backup its SQL database:</li>
|
||||
</ul>
|
||||
<pre><code>bash /var/vmail/backup/backup_sogo.sh
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>Open file <code>/etc/yum.repos.d/sogo.repo</code>, change the version number in
|
||||
<code>baseurl=</code> line from <code>3</code> to <code>4</code>:</li>
|
||||
</ul>
|
||||
<pre><code>baseurl=https://packages.inverse.ca/SOGo/nightly/4/rhel/$releasever/$basearch/
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>Upgrade SOGo packages:</li>
|
||||
</ul>
|
||||
<pre><code>yum clean all
|
||||
yum update sogo* sope*
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>Run the script shipped in SOGo-4.x to update SQL structure:</p>
|
||||
<ul>
|
||||
<li>For LDAP and MySQL/MariaDB backends:</li>
|
||||
</ul>
|
||||
<p><code>bash /usr/share/doc/sogo-4.*/sql-update-3.2.10_to_4.0.0-mysql.sh</code></p>
|
||||
<ul>
|
||||
<li>For PostgreSQL backend:</li>
|
||||
</ul>
|
||||
<p><code>bash /usr/share/doc/sogo-4.*/sql-update-3.2.10_to_4.0.0.sh</code></p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Restart SOGo service:</p>
|
||||
</li>
|
||||
</ul>
|
||||
<pre><code>service sogod restart
|
||||
</code></pre>
|
||||
|
||||
<h2 id="upgrade-sogo-on-debianubuntu">Upgrade SOGo On Debian/Ubuntu</h2>
|
||||
<ul>
|
||||
<li>Backup config files first:</li>
|
||||
</ul>
|
||||
<pre><code>mkdir -p /root/sogo-backup/{sogo,default}
|
||||
cp /etc/sogo/* /root/sogo-backup/sogo/
|
||||
cp /etc/default/sogo /root/sogo-backup/default/
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>Backup its SQL database:</li>
|
||||
</ul>
|
||||
<pre><code>bash /var/vmail/backup/backup_sogo.sh
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>Open file <code>/etc/apt/sources.list</code>, change the version number <code>3</code> to <code>4</code>, like
|
||||
below:</li>
|
||||
</ul>
|
||||
<pre><code># Debian
|
||||
https://packages.inverse.ca/SOGo/nightly/4/debian ...
|
||||
|
||||
# Ubuntu
|
||||
https://packages.inverse.ca/SOGo/nightly/4/ubuntu ...
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>Upgrade SOGo packages:</li>
|
||||
</ul>
|
||||
<pre><code>apt-get update
|
||||
apt-get install --only-upgrade sogo sogo-activesync
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>Run the script shipped in SOGo-4.x to update SQL structure:</p>
|
||||
<ul>
|
||||
<li>For LDAP and MySQL/MariaDB backends:</li>
|
||||
</ul>
|
||||
<p><code>bash /usr/share/doc/sogo/sql-update-3.2.10_to_4.0.0-mysql.sh</code></p>
|
||||
<ul>
|
||||
<li>For PostgreSQL backend:</li>
|
||||
</ul>
|
||||
<p><code>bash /usr/share/doc/sogo/sql-update-3.2.10_to_4.0.0.sh</code></p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Restart SOGo service:</p>
|
||||
</li>
|
||||
</ul>
|
||||
<pre><code>service sogo restart
|
||||
</code></pre>
|
||||
|
||||
<h2 id="upgrade-sogo-on-freebsd">Upgrade SOGo On FreeBSD</h2>
|
||||
<p>FreeBSD ports tree still ships SOGo-3, so no SQL structure change after you
|
||||
update ports <code>www/sogo3</code> and <code>www/sogo3-activesync</code>.</p>
|
||||
<h2 id="upgrade-sogo-on-openbsd">Upgrade SOGo On OpenBSD</h2>
|
||||
<p>OpenBSD 6.3 still ships SOGo-3, so no SQL structure change after you update
|
||||
sogo/sope packages with <code>pkg_add</code> command.</p>
|
||||
<h2 id="troubleshooting">Troubleshooting</h2>
|
||||
<p>If SOGo doesn't work as expected, please check its log file
|
||||
<code>/var/log/sogo/sogo.log</code>. If you don't understand what the error message means,
|
||||
please extract related error message and post to our online support forum:
|
||||
<a href="https://forum.iredmail.org/">https://forum.iredmail.org/</a>.</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