2019-02-23 21:04:08 -06:00
<!DOCTYPE html>
< html >
< head >
< meta http-equiv = "Content-Type" content = "text/html; charset=utf-8" / >
< title > Upgrade iRedMail from 0.9.9 to 1.0< / 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-099-to-10" > Upgrade iRedMail from 0.9.9 to 1.0< / h1 >
< div class = "toc" >
< ul >
< li > < a href = "#upgrade-iredmail-from-099-to-10" > Upgrade iRedMail from 0.9.9 to 1.0< / 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 >
2019-06-23 20:10:39 -05:00
< li > < a href = "#upgrade-iredapd-postfix-policy-server-to-the-latest-stable-release" > Upgrade iRedAPD (Postfix policy server) to the latest stable release< / a > < / li >
2019-03-28 22:33:30 -06:00
< li > < a href = "#upgrade-iredadmin-open-source-edition-to-the-latest-stable-release-096" > Upgrade iRedAdmin (open source edition) to the latest stable release (0.9.6)< / a > < / li >
2019-02-23 21:04:08 -06:00
< li > < a href = "#upgrade-mlmmjadmin-to-the-latest-stable-release-21" > Upgrade mlmmjadmin to the latest stable release (2.1)< / a > < / li >
< li > < a href = "#upgrade-roundcube-webmail-to-the-latest-stable-release" > Upgrade Roundcube webmail to the latest stable release< / a > < / li >
2019-05-22 19:32:14 -05:00
< li > < a href = "#upgrade-netdata-to-the-latest-stable-release-1150" > Upgrade netdata to the latest stable release (1.15.0)< / a > < / li >
2019-07-09 03:24:42 -05:00
< li > < a href = "#fixed-improper-order-of-postfix-smtpd_sender_restriction-rules" > Fixed: improper order of Postfix smtpd_sender_restriction rules< / a > < / li >
2019-02-24 22:39:12 -06:00
< li > < a href = "#fail2ban-slightly-loose-filter-rule-for-postfix" > Fail2ban: slightly loose filter rule for postfix< / a > < / li >
2019-03-24 20:04:23 -06:00
< li > < a href = "#optional-enable-srs-sender-rewriting-scheme-support-in-postfix" > [OPTIONAL] Enable SRS (Sender Rewriting Scheme) support in Postfix< / a > < / li >
2019-02-23 21:04:08 -06:00
< / ul >
< / li >
< / ul >
< / li >
< / ul >
< / div >
2019-02-24 22:39:12 -06:00
< div class = "admonition warning" >
< p class = "admonition-title" > Warning< / p >
< p > This is still a < strong > DRAFT< / strong > document, do < strong > NOT< / strong > apply it.< / p >
< / div >
2019-02-23 21:04:08 -06:00
< 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 >
< p > TODO< / p >
< 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.0
< / code > < / pre >
2019-06-23 20:10:39 -05:00
< h3 id = "upgrade-iredapd-postfix-policy-server-to-the-latest-stable-release" > Upgrade iRedAPD (Postfix policy server) to the latest stable release< / h3 >
2019-02-23 21:04:08 -06:00
< div class = "admonition attention" >
< p class = "admonition-title" > Attention< / p >
2019-03-28 22:33:30 -06:00
< p > iRedAPD offers SRS (Sender Rewriting Scheme) support in this release, by
it's disabled by default, please read our tutorial to understand known
issues and how to enable it.< / p >
2019-02-23 21:04:08 -06:00
< / div >
2019-03-28 22:33:30 -06:00
< 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-096" > Upgrade iRedAdmin (open source edition) to the latest stable release (0.9.6)< / h3 >
2019-02-23 21:04:08 -06:00
< 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-mlmmjadmin-to-the-latest-stable-release-21" > Upgrade mlmmjadmin to the latest stable release (2.1)< / h3 >
< p > Please follow below tutorial to upgrade mlmmjadmin to the latest stable release:
< a href = "./upgrade.mlmmjadmin.html" > Upgrade mlmmjadmin to the latest stable release< / a > < / p >
< h3 id = "upgrade-roundcube-webmail-to-the-latest-stable-release" > Upgrade Roundcube webmail to the latest stable release< / 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 >
2019-05-22 19:32:14 -05:00
< h3 id = "upgrade-netdata-to-the-latest-stable-release-1150" > Upgrade netdata to the latest stable release (1.15.0)< / h3 >
2019-02-24 22:39:12 -06:00
< p > If you have netdata installed, you can upgrade it by following this tutorial: < a href = "./upgrade.netdata.html" > Upgrade netdata< / a > .< / p >
2019-07-09 03:24:42 -05:00
< h3 id = "fixed-improper-order-of-postfix-smtpd_sender_restriction-rules" > Fixed: improper order of Postfix smtpd_sender_restriction rules< / h3 >
< p > iRedMail-0.9.9 and earlier releases didn't configure Postfix to apply custom
restriction rule before querying DNS records of sender domain,
this way you cannot whitelist some sender mail domains which don't have
DNS records (especially your internal mail domains used in LAN). Please follow
steps below to fix it.< / p >
< ul >
< li > Open file < code > /etc/postfix/main.cf< / code > (Linux/OpenBSD) or
< code > /usr/local/etc/postfix/main.cf< / code > (FreeBSD), find parameter
< code > smtpd_sender_restrictions< / code > like below:< / li >
< / ul >
< pre > < code > smtpd_sender_restrictions =
reject_unknown_sender_domain
...
check_sender_access pcre:...
< / code > < / pre >
< ul >
< li > Move the < code > reject_unknown_sender_domain< / code > line after < code > check_sender_access< / code > line
like below:< / li >
< / ul >
< pre > < code > smtpd_sender_restrictions =
...
check_sender_access pcre:...
reject_unknown_sender_domain
< / code > < / pre >
< ul >
< li > Reloading or restarting Postfix service is required.< / li >
< / ul >
2019-02-24 22:39:12 -06:00
< h3 id = "fail2ban-slightly-loose-filter-rule-for-postfix" > Fail2ban: slightly loose filter rule for postfix< / h3 >
< p > We received few reports from clients that Outlook for macOS may trigger some
unexpected smtp errors, and caught by the Fail2ban filter rules shipped by
iRedMail, so we decide to remove the filter rule used to match Postfix log
< code > lost connection after EHLO< / code > .< / p >
< p > Please follow commands below to get the updated filter rules.< / p >
< ul >
< li > On Linux:< / li >
< / ul >
< pre > < code > cd /etc/fail2ban/filter.d/
wget -O postfix.iredmail.conf https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/fail2ban/filter.d/postfix.iredmail.conf
2019-02-27 17:48:46 -06:00
wget -O dovecot.iredmail.conf https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/fail2ban/filter.d/dovecot.iredmail.conf
2019-02-24 22:39:12 -06:00
< / code > < / pre >
2019-03-24 20:04:23 -06:00
< p > Restarting Fail2ban service is required.< / p >
< h3 id = "optional-enable-srs-sender-rewriting-scheme-support-in-postfix" > [OPTIONAL] Enable SRS (Sender Rewriting Scheme) support in Postfix< / h3 >
< p > After you have iRedAPD upgraded to version 2.5, it will listen on 2 new network
ports: 7778 and 7779. They're used by Postfix for SRS (Sender Rewriting Scheme).
For technical details of SRS, please read this paper:
< a href = "https://www.libsrs2.org/srs/srs.pdf" > The Sender Rewriting Scheme (PDF)< / a > .< / p >
< p > To enable SRS support, please add parameters below in Postfix config file
< code > /etc/postfix/main.cf< / code > (on Linux/OpenBSD) or < code > /usr/local/etc/postfix/main.cf< / code >
(on FreeBSD):< / p >
< pre > < code > sender_canonical_maps = tcp:127.0.0.1:7778
sender_canonical_classes = envelope_sender
recipient_canonical_maps = tcp:127.0.0.1:7779
recipient_canonical_classes= envelope_recipient,header_recipient
< / code > < / pre >
< p > Reloading or restarting Postfix service is required.< / p >
< div class = "admonition note" >
< p class = "admonition-title" > Known Issues< / p >
< ul >
< li >
< p > Sender addresses will always be rewritten even if the mail is not
forwarded at all. This is because the canonical maps are read by the
Postfix cleanup daemon, which processes mails at the very beginning
before any routing decision is made.< / p >
< / li >
< li >
< p > Postfix will use rewritten address in the < code > Return-Path:< / code > header, if you
have any sieve rules based on < code > Return-Path:< / code > , it MAY not work anymore and
please update your sieve rules to match rewritten address.< / p >
< / li >
< / ul >
< / div > < div class = "footer" >
2019-02-23 21:04:08 -06:00
< 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 >
