Dear all,

iRedAdmin-Pro-SQL-4.2 (iRedAdmin-Pro for MySQL, MariaDB and PostgreSQL backends) is now available for upgrading and purchasing. This is a small bug fix release, but this bug may affect other features and cause SQL data integrity, so we think it's necessary to release a new version as soon as possible.

• IMPORTANT NOTE: Please upgrade iRedMail to the latest iRedMail-1.0 BEFORE upgrading iRedAdmin-Pro.

• Upgrade tutorials for iRedAdmin-Pro are available here: http://www.iredmail.org/docs/migrate.or … admin.html

How to download the latest iRedAdmin-Pro

If you deployed iRedMail server with the iRedMail Easy platform, there's a upgrade available for your server, upgrading the server will get you the latest iRedAdmin-Pro.

If you deployed iRedMail with the standalone iRedMail installer, you can get download link of this new release by following steps below:

• Login to iRedAdmin-Pro as global admin

• Click "License" on the top-right corner, it will show you basic license info and a "Download" button if new version is available for upgrading.

If above steps don't work for you, please send an email to support @ iredmail.org to get download link of the latest release.

Below are detailed changes since iRedAdmin-Pro-SQL-4.1.2:

RESTful API

• Fixed: resetting mail forwarding (with `forwarding=`) generates incorrect SQL record.

Improvements

• Allow to mark domain as backup mx without specifying primary mx (Postfix will query DNS record to get primary mx).

• Normal admin can not set min/max password lengths shorter/longer than global settings.

• Able to disallow normal admin to manage min/max password lengths.

• Able to view banned IP addresses (in Fail2ban). Note: This is available only when you setup iRedMail server with iRedMail Easy platform.

Fixed issues

• Not store password last change date while updating user password via RESTful API.

• Not correctly remove user profiles while iRedAPD and Amavisd are disabled.

• Modified irrelevant  settings while updating admin profile.