Issue Config check in Plesk Email Security doesn't respect custom `dkimDefaultSelector` setting?

[jnthn]

Server operating system version

AlmaLinux 10.1

Plesk version and microupdate number

18.0.77

I modified my default DKIM selector to a custom one using dkimDefaultSelector in panel.ini (as documented here). However, after that change, the "Config Check" tab in the Plesk Email Security extension shows a red status for the DKIM setup of all my domains (tooltip: "No DKIM policy defined").

Is it possible that the Plesk Email Security extension doesn't respect the custom dkimDefaultSelector selector? Is this something that could be resolved? Or is it recommended to stick to the default selector (default) instead?

 

[Sebahat.hadzhi]

Hi, @jnthn . I can't seem to be able to replicate the issue after changing the DKIM selector via panel.ini. Can you please provide steps to reproduce, along with the selector you configured and DKIM generator used (if any)? Thanks in advance.

 

[jnthn]

@Sebahat.hadzhi Thanks for your reply! I took the following steps yesterday:

1. Updated dkimDefaultSelector in panel.ini (using my brand name)
2. Observed that the DKIM keys weren't changed for existing domains
3. Manually created a new DKIM key for my existing domains in the mail settings and selected it as default
4. Deleted the old DKIM key (default) from existing domains in the mail settings
5. Opened the Plesk Email Security and observed the red status

If needed, I can do some more troubleshooting (like trying out if it works differently when adding a new domain, so Plesk would create the key with the custom selector itself).

 

[Sebahat.hadzhi]

Thank you for the details. I would like to confirm a few more details, please:
1. Did the DKIM status change right after you updated the selector or was it the same before?
2. Are the DNS zones of the affected domains local or remote?

 

[jnthn]

@Sebahat.hadzhi

1. I didn't check it immediately after the change. However, I know that they were green in the days before, and red after the change.
2. They are all local.

I just deleted one of the domains I use for testing while setting up my new server, and added it again. This time, the dkimDefaultSelector option was already active when creating the domain, so the custom selector was used from the beginning. In the end, Plesk Email Security still showed a red status for the domain.

The only domain showing a green status for DKIM, is the one that is still using default as selector.

 

[jnthn]

@Sebahat.hadzhi I was wondering if you have seen my last reply? The issue is still persisting (I'm seeing a red status for DKIM), while I'm sure the configuration is actually correct (I confirmed that with external validation tools).

 

[Sebahat.hadzhi]

Hi, @jnthn . Apologies for not following up on this. I was able to replicate the issue and opened an internal report for our engineers to confirm whether this is a bug or expected behavior. I will share an update once I have some details. Thank you for your patience in the meantime.