iRedMail
// Document IndexWarning
This is still a DRAFT document, do NOT apply it.
Paid Remote Upgrade Support
We offer remote upgrade support if you don't want to get your hands dirty, check the details and contact us.
TODO
/etc/iredmail-release with new iRedMail version numberiRedMail 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.0
Attention
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.
Please follow below tutorial to upgrade iRedAPD to the latest stable release: Upgrade iRedAPD to the latest stable release
Please follow this tutorial to upgrade iRedAdmin open source edition to the latest stable release: Upgrade iRedAdmin to the latest stable release
Please follow below tutorial to upgrade mlmmjadmin to the latest stable release: Upgrade mlmmjadmin to the latest stable release
Roundcube 1.3
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:
If you have netdata installed, you can upgrade it by following this tutorial: Upgrade netdata.
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.
/etc/postfix/main.cf (Linux/OpenBSD) or
/usr/local/etc/postfix/main.cf (FreeBSD), find parameter
smtpd_sender_restrictions like below:smtpd_sender_restrictions =
reject_unknown_sender_domain
...
check_sender_access pcre:...
reject_unknown_sender_domain line after check_sender_access line
like below:smtpd_sender_restrictions =
...
check_sender_access pcre:...
reject_unknown_sender_domain
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
lost connection after EHLO.
Please follow commands below to get the updated filter rules.
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
wget -O dovecot.iredmail.conf https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/samples/fail2ban/filter.d/dovecot.iredmail.conf
Restarting Fail2ban service is required.
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: The Sender Rewriting Scheme (PDF).
To enable SRS support, please add parameters below in Postfix config file
/etc/postfix/main.cf (on Linux/OpenBSD) or /usr/local/etc/postfix/main.cf
(on FreeBSD):
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
Reloading or restarting Postfix service is required.
Known Issues
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.
Postfix will use rewritten address in the Return-Path: header, if you
have any sieve rules based on Return-Path:, it MAY not work anymore and
please update your sieve rules to match rewritten address.