• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Change DKIM key from 1024 to 2048

AgustinLorenzo

New Pleskian
Server operating system version
Debian 12.5
Plesk version and microupdate number
18.0.58 #2
Hi guys,

I have tried to follow the guide to change the size of the DKIM key from 1024 bits to 2048 bits and it has had no effect, when I check with mail-tester.com I get the same key, and I do not see the contents of the folder " /etc/domainkeys/domain/default" has been altered

Guides: https://support.plesk.com/hc/en-us/...n-Plesk-without-causing-mail-delivery-outages and https://support.plesk.com/hc/en-us/...outgoing-emails-of-particular-domain-in-Plesk

Am I doing something wrong or is it some Plesk bug?

Regards, Agustin
 
When you change the configuration, the change is only applied for newly generated DKIM keys.
 
Hi Peter Debik,

Thanks for approve my first post in Plesk forum :)

what I understand following this guide (https://support.plesk.com/hc/en-us/...n-Plesk-without-causing-mail-delivery-outages) is that the dkim keys can be changed from 1024 to 2048 for current subscriptions, apart from being the default for new subscriptions.

and when the procedure is performed:

/usr/local/psa/bin/domain_pref --update example.com -sign_outgoing_mail false
/usr/local/psa/bin/domain_pref --update example.com -sign_outgoing_mail true

The only thing that happens is that the DNS record disappears and the same record appears.

Regards, Agustin
 
Hi again,

As a solution, I don't know if it would be valid:

1º: /usr/local/psa/bin/domain_pref --update example.com -sign_outgoing_mail false
2º: delete all the contents of the "/etc/domainkeys" folder
3º: /usr/local/psa/bin/domain_pref --update example.com -sign_outgoing_mail true

and with this I think that the private key would indeed go to 2048 bits, but the public key would remain at 1024 bits, how would this public key be rotated/updated?

Regards, Agustin
 
Hi guys,

Coming back to this topic it seems that the (official) procedure changed as of version 18.0.56 and now it is:

- Change TTL to 60 seconds in DKIM entry
- Create new DKIM selector and change to this new one
- Delete old DKIM selector (default)
- Re-create DKIM selector with name "default" and change back to this selector.

There is a way to do it in a more friendly way via CLI because in servers with many subscriptions it can be very long and tedious to do, and the change to 2048 keys is almost mandatory to deal with some administrations in some countries.

Link: https://support.plesk.com/hc/en-us/...n-Plesk-without-causing-mail-delivery-outages

Best regards.
 
Back
Top