diff --git a/en_US/upgrade/0-upgrade.iredmail.0.9.6-0.9.7.md b/en_US/upgrade/0-upgrade.iredmail.0.9.6-0.9.7.md index 6b48aaca..cc2d266b 100644 --- a/en_US/upgrade/0-upgrade.iredmail.0.9.6-0.9.7.md +++ b/en_US/upgrade/0-upgrade.iredmail.0.9.6-0.9.7.md @@ -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. diff --git a/en_US/upgrade/0-upgrade.iredmail.0.9.7-0.9.8.md b/en_US/upgrade/0-upgrade.iredmail.0.9.7-0.9.8.md index b66505e5..4b0b1b09 100644 --- a/en_US/upgrade/0-upgrade.iredmail.0.9.7-0.9.8.md +++ b/en_US/upgrade/0-upgrade.iredmail.0.9.7-0.9.8.md @@ -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 (), 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 ``` diff --git a/en_US/upgrade/0-upgrade.sogo.3.to.4.md b/en_US/upgrade/0-upgrade.sogo.3.to.4.md new file mode 100644 index 00000000..56252a74 --- /dev/null +++ b/en_US/upgrade/0-upgrade.sogo.3.to.4.md @@ -0,0 +1,122 @@ +# Upgrade SOGo from v3 to v4 + +[TOC] + +SOGo v4 was released on Mar 7, 2018 by the SOGo team (), 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: +. diff --git a/html/upgrade.iredmail.0.9.7-0.9.8.html b/html/upgrade.iredmail.0.9.7-0.9.8.html index a9612435..ef542f1e 100644 --- a/html/upgrade.iredmail.0.9.7-0.9.8.html +++ b/html/upgrade.iredmail.0.9.7-0.9.8.html @@ -23,12 +23,15 @@
  • General (All backends should apply these steps) @@ -67,6 +70,8 @@ check the details and

    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.
      • @@ -93,6 +98,41 @@ so that you can know which version of iRedMail you're running. For example:

      Upgrade iRedAPD (Postfix policy server) to the latest stable release (2.2)

      Please follow below tutorial to upgrade iRedAPD to the latest stable release: Upgrade iRedAPD to the latest stable release

      +

      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

      +

      Upgrade Roundcube webmail to the latest stable release (1.3.5)

      +
      +

      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:

      + +

      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.

      +

      Fixed: SOGo backup script contains 3 issues

      SOGo backup script /var/vmail/backup/backup_sogo.sh shipped in iRedMail-0.9.7 and earlier releases contains 3 issues:

      @@ -290,14 +330,14 @@ a range from 127.0.0.2 to 127.0.0.11), so we should ch

      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
      diff --git a/html/upgrade.sogo.3.to.4.html b/html/upgrade.sogo.3.to.4.html new file mode 100644 index 00000000..a471feee --- /dev/null +++ b/html/upgrade.sogo.3.to.4.html @@ -0,0 +1,156 @@ + + + + + Upgrade SOGo from v3 to v4 + + + + +

      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 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/.

      +

      All documents are available in BitBucket repository, and published under Creative Commons license. You can download the latest version for offline reading. If you found something wrong, please do contact us to fix it.

      +
      + + + + \ No newline at end of file