Resolved Plesk 18.0.70 Update 1: DKIM setup not possible on newly added domains

[bgptbg]

Server operating system version

Ubuntu 22.04.5 LTS, Ubuntu 20.04.6 LTS, CentOS Linux 7.9.2009

Plesk version and microupdate number

18.0.70 #1

After updating to Plesk 18.0.70 Update 1, it is no longer possible to activate DKIM for newly added domains. The default DKIM selector (Plesk default) is not supported, and creating a new selector is also not possible. This behavior has been confirmed on Ubuntu 22.04.5 LTS, Ubuntu 20.04.6 LTS, and CentOS Linux 7.9.2009.

 

[Mark_NLD]

We are seeing the same bug on all our updated Plesk systems.

Workaround:

1. create a new dkim key with name selector1 (or something else)
2. activate and save
3. create a new dkim key with name default
4. activate and save
5. delete dkim key selector1

 

[Mark_NLD]

@bgptbg Plesk was able to reproduce it in their test environment on a newly created domain. Their development team has started an investigation which takes 2-3 business days.

 

[Sebahat.hadzhi]

Our team released an update today which fixes the issue with the statistics calculation. If you have automatic updates enabled this update should be installed automatically overnight. Plesk Obsidian 18.0.70 Update 2:

Fixed the issue where enabling the “Use DKIM spam protection system to sign outgoing email messages” option on a Plesk server with no DNS server installed would fail with the “This option is not supported” error. (PPP-68661)