• 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.

How to switch on DomainKeys support on every domain..

S

S.Celik

Guest
Is there a group operation to do this? Or how do i switch on domainkeys support on old and new domains automaticly?
 
Do you have this sorted yet? If so let me know, if not, i might have to just find a way
 
Bingo. I was looking in Parameters table in PSA dbase but couldn't work out why it was only listed as domain_keys_sign = true if they had a mail account setup.
 
For anyone who is looking for command line interface about domainkeys:
(it says, "available since Plesk 8.4" but i was looking for it since 8.4 also :))

-sign_outgoing_mail


true|false


Allows/Prohibits using DomainKeys spam protection on a domain.

Is false by default.

Available since Plesk 8.4.


To use DomainKeys spam protection on the domain example.com:

# ./domain_pref -u example.com -sign_outgoing_mail true
 
Back
Top