Resolved Plesk does not retain DKIM keys during server migration

[TorbHo]

@Sebahat.hadzhi great news. Thank you!

 

[brother4]

@Sebahat.hadzhi Could there be an error here? I have now transferred the keys using Plesk Migrator, but I am getting the following error:

Repairing the mail server configuration
Reconfiguring all domains and mailboxes ......................... [2026-02-04 20:39:05.378] 1234 ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/mchk'] with exit code [1]
[FAILED]

Errors occured in mail restore procedure
Some utilities have exited with errors:
/usr/lib/plesk-9.0/mail_dk_restore
E: example.com: key file /etc/domainkeys/example.com/default
doesn't exist or not a file: No such file or directory
Try to fix it by running: plesk repair mail example.com

And with: plesk repair mail example.com -y

Unable to find row with id 0 in dns_zone table.

It doesn't matter whether I have installed the Plesk DNS component or not (I use an external DNS).

Before migrating to the new server, DKIM was working perfectly. Currently, after the migration, no emails are being signed with DKIM.

The key is not default for me, but hosting, and is also entered correctly in Plesk and via DNS. The private key is also located on the server under the name after migration and is still identical to before. => /etc/domainkeys/example.com/hosting

Plesk Obsidian 18.0.75 Web Host Edition - Ubuntu 24.04.3 LTS

 

[brother4]

I performed these steps:

Installed DNS service (plesk component)
Waited until the installation process was complete, terminating it if necessary
Created a symbolic link from hosting to default dkim private key
Ran Plesk repair (ran now without errors)
After that, outgoing emails were correctly signed with hosting again.

I suspect there are still bugs in Migrator if you don't transfer the DNS component (I assumed that you didn't need external DNS and should actually be the case). Apparently, the mail repair program wants to access its database entries.

In addition, there is the default key issue if you have a different name.

It took me a few hours to figure out how and where the problem lies.

 

[Sebahat.hadzhi]

@brother4 , do I correctly understand that BIND DNS was not present on the destination server at time of the issue? Were there any DNS extensions present at the time, please? Thanks.