• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

DKIM

stefanoostwegel

Basic Pleskian
Hello,

I really want DKIM to work with Plesk 12.5 CentOS6, postfix and Qmail.
I have found some solutions to get some of it work, but my customers cannot use that, everything has to be configured manually!
When will this support come to Plesk?
Anny sugestions for automation in the DKIM support?

Thanks
 
Believe it or not but that option is there on the latest version of Plesk 12.5, not sure how long it's been there for since it's not in the change logs and seems to work pretty good. Can find it by going into your domain and click on Mail Settings. You'll find a checkbox saying "Use DomainKeys spam protection system to sign outgoing email messages" (need to make sure you enable it first by going to Tools and Settings, Mail Server Settings, and put a checkmark next to "Allow signing outgoing mail" under the "DomainKeys spam protection" section). More info at https://docs.plesk.com/en-US/12.5/administrator-guide/mail/antispam-tools/domainkeys-protection/
 
Believe it or not ;) but this option is DomainKey NOT DKIM (DomainKeys is predecessor of DKIM)
and this Option is since Plesk 12.0.18
 
Eh you know what your right. It's been a long night last night. I'll just make my exit now.
 
Back
Top