3.7 KiB

Raw Blame History

Upgrade iRedMail from 1.3.1 to 1.3.2

[TOC]

!!! warning

THIS IS 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

XXX 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.2

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

The recent iRedAPD-4.0 and 4.1 contain a critical bug which causes temporarily rejection, this new release fixes it.

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

Upgrade Roundcube webmail to the latest stable release (1.4.7)

!!! warning "Roundcube 1.4"

Since Roundcube 1.3, at least __PHP 5.4__ is required. If your server is
running PHP 5.3 and cannot upgrade to 5.4, please upgrade Roundcube
the latest 1.2 branch instead.

Roundcube 1.4.6 fixes few security issues, 1.4.7 fixes a new one. All users are encouraged to upgrade as soon as possible.

How to upgrade Roundcube.

References:

05 July 2020, Security updates 1.4.7, 1.3.14 and 1.2.11 released
07 June 2020, Updates 1.4.6 and 1.3.13 released
02 June 2020, Security updates 1.4.5 and 1.3.12 released

Upgrade netdata to the latest stable release (1.23.2)

If you have netdata installed, you can upgrade it by following this tutorial: Upgrade netdata.

Fixed: update Fail2ban filter rules to match new error log produced by latest Roundcube

Please run commands below as root user to get latest filter file for Roundcube:

cd /etc/fail2ban/filter.d/
wget -O roundcube.iredmail.conf https://raw.githubusercontent.com/iredmail/iRedMail/1.3.1/samples/fail2ban/filter.d/roundcube.iredmail.conf

Restarting fail2ban service is required.

Fixed: can not store mail sender address with utf8 characters in `amavisd` database

In amavisd database, column msgs.from_address is defined as VARCHAR(255), it doesn't support emoji characters. Please login to MySQL/MariaDB server as root user or amavisd user, then run SQL commands below to fix it:

USE amavisd;
ALTER TABLE msgs MODIFY COLUMN from_address VARBINARY(255) NOT NULL DEFAULT '';

[OPTIONAL] Amavisd: Log matched virus database name

Please update parameter @av_scanner in Amavisd config file as described below, so that Amavisd logs matched virus database name. - On RHEL/CentOS, it's /etc/amavisd/amavisd.conf - On Debian/Ubuntu, it's /etc/amavis/conf.d/50-user - On FreeBSD, it's /usr/local/etc/amavisd.conf - On OpenBSD, it's /etc/amavisd.conf

Find parameter @av_scanner like below:

@av_scanners = (
    ...
    qr/\bOK$/, qr/\bFOUND$/,
    qr/^.*?: (?!Infected Archive)(.*) FOUND$/ ],
);

Please append character m after OK$/ and FOUND$/ like below:

@av_scanners = (
    ...
    qr/\bOK$/m, qr/\bFOUND$/m,
    qr/^.*?: (?!Infected Archive)(.*) FOUND$/m ],
);

Restarting Amavisd service is required.

3.7 KiB Raw Blame History