Question Dkim error when creating Custumers if remote email service is SmarterMail

[majidalizadeh.yb]

Server operating system version

Windows Server 2022

Plesk version and microupdate number

Plesk Obsidian version 18.0.69 Update #3

Greetings
I recently noticed that on several different servers, creating new domains when Allow signing outgoing mail is enabled in the Plesk panel is accompanied by an error and the domain is not created.
The operating system of these machines is Windows 2022 and the mail server is remote (SmarterMail remote support: on).
They have Plesk Obsidian version 18.0.69 Update #3 of the Plesk panel and the Smartermail servers have different versions.

SmarterMail Professional 100.0.8629.18139 (August 17, 2023)
SmarterMail Professional Version - 100.0.7242.24590
SmarterMail Professional 100.0.8594.33598 (July 13, 2023)

The error text is as follows.

Email Configuration
mailmng failed: Invalid content type: extract_string must be text and extract_json must be JSON. in generateDKIMKeyPair(default, 2048)(SmarterMail::Common:omain::generateDKIMKeyPair line 199)
in Unable to execute console command: '--generate-domain-dkim-key-pair'(vconsoleapp::start line 95)
in Unable to execute command: '"C:\Program Files (x86)\Plesk\admin\bin\mailmng" --generate-domain-dkim-key-pair "--domain-name=test55256.com" "--key-size=2048" "--selector=default"'(vconsoleapp::run line 117)
(Error code 1)

What do you think? What is your solution?

 

[scsa20]

I deleted my last post since I just realized that the bug in question was already patched since version 18.0.52 derpy derp derp. In that case, have you tried turning off the allow signing outgoing mail first, create the domain, then enabling it?

Also, not sure which one of the servers you're having the issue with but if the ones having the issue is the one running a lower version of SmarterMail (anything below 100.0.8495) and all the plesk versions is running anything above 18.0.52 then that could explain why since smartermail updated it's api in version 100.0.8495 and plesk updated to utilize the new apis in version 18.0.52.

 

[Sebahat.hadzhi]

It is very likely due to incompatibility. @majidalizadeh.yb , can you please update SmartMail to the latest build. If it is not possible to update the SmartMail version at this point, the workaround you can try is to disable “Allow signing outgoing mail” in Tools & Settings -> Mail Server Settings.

 

[majidalizadeh.yb]

By disabling "Allow signing outgoing mail", a new domain or Custumers is added. But the problem is that the DKIM record cannot be ignored and I cannot clear the issue.
The problem is present in all three versions of SmarterMail. I even raised this issue with Smartertools and they said "For this issue, you will need to reach out to Plesk as they developed this integration and should be able to fix it."
Another thing is that I only upgraded Plesk to a higher version at the server level when I encountered this problem, and no changes were made to Smartermail.
Do you have a solution to fix this problem or has the problem been identified at all that will be fixed in future versions?
If providing you with information helps in identifying and fixing the problem, please let me know.
@scsa20
@Sebahat.hadzhi

 

[Sebahat.hadzhi]

Thank you for the update, @majidalizadeh.yb . The issue might be caused due to SmarterMail being unable to generate a DKIM key with 2048 bit length.

Please try adding the following line to panel.ini[ICODE] at C:\Program Files (x86)\Plesk\admin\conf\[/ICODE]:

[mail]
dkimKeySize = 1024

If the issue still persists, I would suggest re-considering an upgrade of the SmarterMail feature as all three mentioned versions are outdated.