iRedMail — EE Upgrade DKIM is changed every upgrade.

Re: EE Upgrade DKIM is changed every upgrade.

null@example.com (ZhangHuangbin) — Wed, 13 May 2026 08:33:40 +0000

Btw, better use our Ticket system for EE issues: https://store.iredmail.org/

Re: EE Upgrade DKIM is changed every upgrade.

null@example.com (ZhangHuangbin) — Wed, 13 May 2026 08:33:23 +0000

Update: This issue has been fixed, the fix will be available in next EE release (v1.7.4).
Thanks for the feedback.

Re: EE Upgrade DKIM is changed every upgrade.

null@example.com (ZhangHuangbin) — Sat, 09 May 2026 01:10:36 +0000

Hi,

Do you use a custom DKIM selector?

EE Upgrade DKIM is changed every upgrade.

null@example.com (Davesworld) — Fri, 08 May 2026 16:23:29 +0000

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version EE 1.7.3
- Deployed with iRedMail Easy or the downloadable installer? No, EE.
- Linux/BSD distribution name and version: Debian Trixie
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): PGSQL
- Web server (Apache or Nginx): NGINX
- Manage mail accounts with iRedAdmin-Pro? No, EE version.
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue. DKIM key is changed with every upgrade.
====

Just a heads up. Every time you upgrade the Enterprise Edition, the DKIM key gets replaced with one that does not honor the DKIM selector one has chosen. One must delete that, then a new key will show up with the DKIM selector, one chosen before the upgrade. Copy and paste that one into the DNS records, and it will match again.

This caught me by surprise on the 1.7.2 update when the postmaster started getting DKIM error domian reports from Google, etc.