New: upgrade.iredmail.1.2.1-1.3.html.
This commit is contained in:
Zhang Huangbin
parent
a86a8db91c
commit
4d13badc83
|
|
@ -0,0 +1,52 @@
|
|||
# Upgrade iRedMail from 1.2.1 to 1.3
|
||||
|
||||
[TOC]
|
||||
|
||||
!!! warning
|
||||
|
||||
THIS IS STILL A DRAFT DOCUMENT, DO NOT APPLY IT.
|
||||
|
||||
!!! note "Paid Remote Upgrade Support"
|
||||
|
||||
We offer remote upgrade support if you don't want to get your hands dirty,
|
||||
check [the details](https://www.iredmail.org/support.html) and
|
||||
[contact us](https://www.iredmail.org/contact.html).
|
||||
|
||||
## ChangeLog
|
||||
|
||||
* May XX, 2020: initial release.
|
||||
|
||||
## General (All backends should apply these changes)
|
||||
|
||||
### Update `/etc/iredmail-release` with new iRedMail version number
|
||||
|
||||
iRedMail stores the release version in `/etc/iredmail-release` after
|
||||
installation, it's recommended to update this file after you upgraded iRedMail,
|
||||
so that you can know which version of iRedMail you're running. For example:
|
||||
|
||||
```
|
||||
1.3
|
||||
```
|
||||
|
||||
### Fixed: inconsistent Fail2ban jail names
|
||||
|
||||
!!! attention
|
||||
|
||||
This is applicable to Linux and OpenBSD.
|
||||
|
||||
iRedMail-1.2 and 1.2.1 introduced [SQL integration in
|
||||
Fail2ban](./fail2ban.sql.html), but there're few inconsistent jail names which
|
||||
caused unbanning IP from iRedAdmin-Pro doesn't work. Please run commands below
|
||||
to fix them.
|
||||
|
||||
```
|
||||
cd /etc/fail2ban/jail.d/
|
||||
perl -pi -e 's#dovecot-iredmail#dovecot#g' dovecot.local
|
||||
|
||||
perl -pi -e 's#postfix-pregreet-iredmail#postfix-pregreet#g' postfix-pregreet.local
|
||||
perl -pi -e 's#name=postfix,#name=postfix-pregreet,#g' postfix-pregreet.local
|
||||
|
||||
perl -pi -e 's#postfix-iredmail#postfix#g' postfix.local
|
||||
perl -pi -e 's#roundcube-iredmail#roundcube#g' roundcube.local
|
||||
perl -pi -e 's#sogo-iredmail#sogo#g' sogo.local
|
||||
```
|
||||
|
|
@ -0,0 +1,84 @@
|
|||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||||
<title>Upgrade iRedMail from 1.2.1 to 1.3</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-iredmail-from-121-to-13">Upgrade iRedMail from 1.2.1 to 1.3</h1>
|
||||
<div class="toc">
|
||||
<ul>
|
||||
<li><a href="#upgrade-iredmail-from-121-to-13">Upgrade iRedMail from 1.2.1 to 1.3</a><ul>
|
||||
<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="#fixed-inconsistent-fail2ban-jail-names">Fixed: inconsistent Fail2ban jail names</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="admonition warning">
|
||||
<p class="admonition-title">Warning</p>
|
||||
<p>THIS IS STILL A DRAFT DOCUMENT, DO NOT APPLY IT.</p>
|
||||
</div>
|
||||
<div class="admonition note">
|
||||
<p class="admonition-title">Paid Remote Upgrade Support</p>
|
||||
<p>We offer remote upgrade support if you don't want to get your hands dirty,
|
||||
check <a href="https://www.iredmail.org/support.html">the details</a> and
|
||||
<a href="https://www.iredmail.org/contact.html">contact us</a>.</p>
|
||||
</div>
|
||||
<h2 id="changelog">ChangeLog</h2>
|
||||
<ul>
|
||||
<li>May XX, 2020: initial release.</li>
|
||||
</ul>
|
||||
<h2 id="general-all-backends-should-apply-these-changes">General (All backends should apply these changes)</h2>
|
||||
<h3 id="update-etciredmail-release-with-new-iredmail-version-number">Update <code>/etc/iredmail-release</code> with new iRedMail version number</h3>
|
||||
<p>iRedMail stores the release version in <code>/etc/iredmail-release</code> after
|
||||
installation, it's recommended to update this file after you upgraded iRedMail,
|
||||
so that you can know which version of iRedMail you're running. For example:</p>
|
||||
<pre><code>1.3
|
||||
</code></pre>
|
||||
|
||||
<h3 id="fixed-inconsistent-fail2ban-jail-names">Fixed: inconsistent Fail2ban jail names</h3>
|
||||
<div class="admonition attention">
|
||||
<p class="admonition-title">Attention</p>
|
||||
<p>This is applicable to Linux and OpenBSD.</p>
|
||||
</div>
|
||||
<p>iRedMail-1.2 and 1.2.1 introduced <a href="./fail2ban.sql.html">SQL integration in
|
||||
Fail2ban</a>, but there're few inconsistent jail names which
|
||||
caused unbanning IP from iRedAdmin-Pro doesn't work. Please run commands below
|
||||
to fix them.</p>
|
||||
<pre><code>cd /etc/fail2ban/jail.d/
|
||||
perl -pi -e 's#dovecot-iredmail#dovecot#g' dovecot.local
|
||||
|
||||
perl -pi -e 's#postfix-pregreet-iredmail#postfix-pregreet#g' postfix-pregreet.local
|
||||
perl -pi -e 's#name=postfix,#name=postfix-pregreet,#g' postfix-pregreet.local
|
||||
|
||||
perl -pi -e 's#postfix-iredmail#postfix#g' postfix.local
|
||||
perl -pi -e 's#roundcube-iredmail#roundcube#g' roundcube.local
|
||||
perl -pi -e 's#sogo-iredmail#sogo#g' sogo.local
|
||||
</code></pre><div class="footer">
|
||||
<p style="text-align: center; color: grey;">All documents are available in <a href="https://github.com/iredmail/docs/">GitHub 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://github.com/iredmail/docs/archive/master.zip">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