After migration DKIM verification fails: dkim=fail (body hash did not verify)

Taras Ermoshin

Updated April 05, 2023 04:02

kb: bug Plesk for Linux ext: migrator ABT: Group B

Applicable to:

After migration DKIM verification fails to send emails to Google, Hotmail or other mail services, as a result, some emails are rejected or classified as SPAM.
At Domains > example.com > DNS Settings: DKIM TXT record default._domainkey.example.com. looks like the following example :

PLESK_INFO: v=DKIM1; p=DKIM1; p=OlDKey..;
New domains created contains a valid DKIM TXT record:

PLESK_INFO: v=DKIM1; p=NeWkEy..;

This is caused by Plesk bug #PPPM-6529 that will be fixed in upcoming Plesk updates.

There are 2 workarounds:

Click on a section to expand

Update the DKIM TXT record on the target's DNS zone for example.com to keep source DKIM TXT record

As a result, record in Domains > example.com > DNS Settings will keep source DKIM key and it should look as follows:

CONFIG_TEXT: v=DKIM1; p=OlDKey..;

Re-create the DKIM TXT record from example.com, to keep target server DKIM TXT record

Log in to Plesk
Go to Domains > example.com > Mail Settings
Disable Use DKIM spam protection system to sign outgoing email messages and save.
Enable again Use DKIM spam protection system to sign outgoing email messages and save.

As a result, record in Domains > example.com > DNS Settings will have a new DKIM key and it should look as follows:

CONFIG_TEXT: v=DKIM1; p=NeWkEy..;