iRedMail — [Fixed as of 1.7.1]EE Edition DKIM forced to use DKIM as the selector.

Re: [Fixed as of 1.7.1]EE Edition DKIM forced to use DKIM as the selector.

null@example.com (Davesworld) — Tue, 31 Mar 2026 02:27:00 +0000

EE version 1.7.1 fixed this. To use the new DKIM selector, one must delete the old key. Once that is deleted, then click on generate new key and press the DKIM button, and put in the desired selector, then you have a new key pair with the selector you want. Now just copy and paste to the registrar exactly as is.

Re: [Fixed as of 1.7.1]EE Edition DKIM forced to use DKIM as the selector.

null@example.com (Davesworld) — Sat, 28 Mar 2026 09:43:20 +0000

ZhangHuangbin wrote:

Hi Davesworld,
- You can generate new DKIM key on EE first, then update SQL table `vmail.dkim`, column `selector`.
- Will support selector customization in next EE release.
- Better use our iRedMail Store website for EE tech support: https://store.iredmail.org/

I am just starting to realize that the ticket system comes with the subscription, but not for heavily complicated stuff, if I read correctly. I look forward to the next version.

Re: [Fixed as of 1.7.1]EE Edition DKIM forced to use DKIM as the selector.

null@example.com (ZhangHuangbin) — Sat, 28 Mar 2026 05:08:02 +0000

Hi Davesworld,

- You can generate new DKIM key on EE first, then update SQL table `vmail.dkim`, column `selector`.
- Will support selector customization in next EE release.
- Better use our iRedMail Store website for EE tech support: https://store.iredmail.org/

Re: [Fixed as of 1.7.1]EE Edition DKIM forced to use DKIM as the selector.

null@example.com (Davesworld) — Sat, 28 Mar 2026 00:29:05 +0000

I submitted a feature request under issues at GIT.

Re: [Fixed as of 1.7.1]EE Edition DKIM forced to use DKIM as the selector.

null@example.com (Davesworld) — Fri, 27 Mar 2026 19:36:07 +0000

I did try to allow dkim._domainkey for two different servers with their respective keys published, and as expected, ran into authentication problems when sending mail from each server.

Each server under one domain must have a unique selector.

What file in the EE web GUI is responsible for forcing DKIM as the selector?

Re: [Fixed as of 1.7.1]EE Edition DKIM forced to use DKIM as the selector.

null@example.com (Davesworld) — Fri, 27 Mar 2026 19:01:17 +0000

After editing the database to have my created DKIM keys with mail as the selector rather than dkim, the system added a second entry with... You guessed it, dkim as the selector. Aaaarrrggghhh!

I cannot imagine this being a good idea for an EE server where multiple servers exist under the same domain. It should be something that is selectable since the system hijacks it.

I hate to have to delete system-added keys in the database to keep only the one I edited wth mail as the selector for my main server.

I just want some control over my server and do not wish to go back to Pro.

[Fixed as of 1.7.1]EE Edition DKIM forced to use DKIM as the selector.

null@example.com (Davesworld) — Thu, 26 Mar 2026 07:21:12 +0000

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

I prefer not to use DKIM as the selector since I have multiple servers on one domain and prefer to use a custom selector. What I don't want is three DKIM records at my registrar, all using the selector DKIM.

The only way I have been able to get around this is to generate a key pair after modifying the file to use a different selector and generating a key pair. Then, going into the database and copying them in place of the existing values. Of course, the web GUI complains when I click on DNS and see that section. were it not for the selector being only DKIM by default, it would be a cakewalk simply copying and pasting to the registrar from the web GUI.