Symptoms
-
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 :
v=DKIM1; p=DKIM1; p=OlDKey..;
-
New domains created contains a valid DKIM TXT record:
v=DKIM1; p=NeWkEy..;
Cause
This is caused by Plesk bug #PPPM-6529 that will be fixed in upcoming Plesk updates.
Resolution
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
-
Go to Domains > example.com > DNS Settings
-
Click on DKIM TXT record: default._domainkey.example.com.
-
Delete
p=DKIM1;from TXT record and save changes.
As a result, record in Domains > example.com > DNS Settings will keep source DKIM key and it should look as follows:
v=DKIM1; p=OlDKey..;
Re-create the DKIM TXT record from example.com, to keep target server DKIM TXT record
-
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:
v=DKIM1; p=NeWkEy..;