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

Formatting.

This commit is contained in:
Zhang Huangbin 2020-06-25 13:50:38 +08:00
parent 3bbe839580
commit 7732cee442
2 changed files with 23 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
en_US/iredmail-easy/4-iredmail-easy.release.notes.md
View File

@ -6,22 +6,23 @@
* Possible issue after upgraded on CentOS 8:
- The new CentOS 8 release, `8.2.2004`, ships Dovecot-2.3.8 recently, it
has some backward-incompatibility issues. iRedMail Easy will upgrade it
from old version `2.2.36` and re-generates its config files.
- Dovecot 2.3 is not fully compatible with old 2.2.x release, it MAY fail
to (re)start if you have unsupported parameters defined in config file
under `/opt/iredmail/custom/dovecot/conf-enabled/`, mostly used one is
parameter `ssl_protocols`, and you must replace it by
`ssl_min_protocol`.
Old CentOS 8 releases shipped Dovecot-2.2.x, but the new `8.2.2004` release
suprisely ships Dovecot-2.3.8 which has some backward-incompatible settings.
iRedMail Easy will upgrade it from old version `2.2.36` and re-generates
its config files, it MAY fail to (re)start if you have unsupported
customized parameters set in config file under
`/opt/iredmail/custom/dovecot/conf-enabled/`.
For example, if you still need to support TLSv1, please set
`ssl_min_protocol = TLSv1` instead. Default value is TLSv1.2.
Mostly customized parameter is `ssl_protocols`, it should be replace by
`ssl_min_protocol`.
- For more details, please check [official Dovecot upgrade
tutorial](https://doc.dovecot.org/installation_guide/upgrading/from-2.2-to-2.3/).
- If you have issue after upgraded, feel free to create a support
ticket on the iRedMail Easy platform.
For example, if you still need to support TLSv1, please set
`ssl_min_protocol = TLSv1` instead. Default value is TLSv1.2.
- For more details, please check [official Dovecot upgrade
tutorial](https://doc.dovecot.org/installation_guide/upgrading/from-2.2-to-2.3/).
- If you have issue after upgraded, feel free to create a support
ticket on the iRedMail Easy platform.
* Supports now distribution releases:
* Ubuntu 20.04. All 3 backends (MariaDB, PostgreSQL, OpenLDAP) are available.

20
html/iredmail-easy.release.notes.html
View File

@ -49,16 +49,14 @@
<ul>
<li>
<p>Possible issue after upgraded on CentOS 8:</p>
<ul>
<li>The new CentOS 8 release, <code>8.2.2004</code>, ships Dovecot-2.3.8 recently, it
has some backward-incompatibility issues. iRedMail Easy will upgrade it
from old version <code>2.2.36</code> and re-generates its config files.</li>
<li>
<p>Dovecot 2.3 is not fully compatible with old 2.2.x release, it MAY fail
to (re)start if you have unsupported parameters defined in config file
under <code>/opt/iredmail/custom/dovecot/conf-enabled/</code>, mostly used one is
parameter <code>ssl_protocols</code>, and you must replace it by
<code>ssl_min_protocol</code>.</p>
<p>Old CentOS 8 releases shipped Dovecot-2.2.x, but the new <code>8.2.2004</code> release
suprisely ships Dovecot-2.3.8 which has some backward-incompatible settings.
iRedMail Easy will upgrade it from old version <code>2.2.36</code> and re-generates
its config files, it MAY fail to (re)start if you have unsupported
customized parameters set in config file under
<code>/opt/iredmail/custom/dovecot/conf-enabled/</code>.</p>
<p>Mostly customized parameter is <code>ssl_protocols</code>, it should be replace by
<code>ssl_min_protocol</code>.</p>
<p>For example, if you still need to support TLSv1, please set
<code>ssl_min_protocol = TLSv1</code> instead. Default value is TLSv1.2.</p>
<ul>
@ -68,8 +66,6 @@
ticket on the iRedMail Easy platform.</li>
</ul>
</li>
</ul>
</li>
<li>
<p>Supports now distribution releases:</p>
<ul>