1

Topic: iRedMail EE - Whitelists/Blacklists

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): iRedMail EE 1.8.1
- Deployed with iRedMail Easy or the downloadable installer? Enterprise Edition
- Linux/BSD distribution name and version: Ubuntu 24.04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro? Enterprise Edition
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

I know the release notes say that 1.8.0 has a "breaking change" that whitelists and blacklists are handled by milter now instead of amavisd, but this note should be more explicit about what that means! It's not just a syntactical breaking change - after upgrading from 1.7.4 to 1.8.1 I found my whitelists and blacklists empty in the iRedMail EE interface.

Thankfully, the data was still there in the amavisd database, but it would have been nice if this data  was converted automatically since it is stored in different tables.

I was able to select the entries out to a text file using mysql, edit them to reflect the new syntax, and add them in via the EE interface. I did it this way rather than scripting it or using SQL in case the EE interface did more than add the entries into milter:wblist.

Can the release notes be clarified, and a migration tool be provided for others? My server-wide lists were only a few dozen entries, but I can imagine that more active servers might have larger lists.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: iRedMail EE - Whitelists/Blacklists

Sorry about this trouble, it was supposed to be migrated during upgrade.

You can migrate whitelists / blacklists with commands below:

cd /opt/iredapd/
python3 migrate_to_milter.py

Next time maybe report issue in our iRedMail Store ticket system first, so that you don't need to handle this manually.