• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Recent content by Justin Ponce

  1. J

    Resolved DKIM/DomainKey with external DNS ?

    True. The issue I'm having right now is they usually end up in the spam/junk folder for gmail, outlook, etc., pre DKIM and of course after. Yes that would be a great feature for the Multi Server Extension for sure. Thanks for looking into this. I'll see what I can do for now.
  2. J

    Resolved DKIM/DomainKey with external DNS ?

    I see. Are you aware of any SMTP relay option available, i.e. making the plesk mailer function "login" to the SMTP server to send emails (thereby fixing the DKIM problem)? Or is that what you meant by recommending I submit a feature request?
  3. J

    Resolved DKIM/DomainKey with external DNS ?

    Understood, here are more details of the issue plaguing me: I'm running, say, half a dozen VPS hosts, each running an installation of Plesk Web Admin or Web Pro depending on their needs. My main domain is fissionblue.com, where I use fissionblue.com and www.fissionblue.com for the company...
  4. J

    Resolved DKIM/DomainKey with external DNS ?

    Hi there UFHH01, I was able to get DKIM working fine on an external DNS using the instructions above (copying the TXT entry from my Plesk-installed DNS BIND zone files). I have one issue that seems to be really impacting me though: The individual domains all have DNS zone files, but the main...
Back
Top