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

Recent content by micheloe

  1. M

    Resolved No DKIM key generated/shown when DNS component is not installed

    The same was happening for me for a domain which already had DKIM active, but had no DKIM keypair yet. After I first turned of DKIM signing and then turned it back on via the CLI, a default DKIM key was generated and the UI now shows an active selector (default) and the "How to configure...
  2. M

    Resolved No DKIM key generated/shown when DNS component is not installed

    I am not sure if this is part of the issue, but so far I haven't been able to find a CLI equivalent for generating a DKIM keypair. It would be nice (read: required) to have this option, as simply disabling/enabling does not suffice.
  3. M

    Forwarded to devs Removal of -bs option from plesk-sendmail-wrapper

    Ok, now that 18.0.45 update 1 is installed, we also get the following error: 554 5.7.1 <[email protected]>: Relay access denied Adding 127.0.0.0/8 to the whitelist solves this indeed, but IMHO this should have been handled by the update.
  4. M

    Forwarded to devs Removal of -bs option from plesk-sendmail-wrapper

    To work around this issue, one can temporarily use: Swift mailer: Symfony mailer: But lets hope for a timely fix from the Plesk devs as this alternative method is not recommended.
  5. M

    Issue Removal of -bs option from plesk-sendmail-wrapper

    Well, that's not very... helpful. :-)
  6. M

    Forwarded to devs Removal of -bs option from plesk-sendmail-wrapper

    I can confirm the same issue with the older and unsupported Swiftmailer, as well as the newer Symfony mailer.
  7. M

    Issue Removal of -bs option from plesk-sendmail-wrapper

    I tried this already, but unfortunately:
  8. M

    Issue Removal of -bs option from plesk-sendmail-wrapper

    Hi, As of Plesk Obsidian 18.0.44 (24 may 2022), and more specifically PPPM-13497 the -bs options appears to be disallowed from the postfix-sendmail-wrapper. I take it this is the "fix" for being able to bypass email sending restrictions? Since this update we encounter the following issues on...
  9. M

    Resolved Plesk upgrade to Obsidian extensions fails because invalid SSL certificate on ext.plesk.com

    Apparently it's solved, thanks!
  10. M

    Resolved Plesk upgrade to Obsidian extensions fails because invalid SSL certificate on ext.plesk.com

    When upgrading Plesk Onyx 17.8 to Obsidian 18.0.23 in CentOS 7, the upgrade fails partially when updating extensions. The issue seems global though, not related to plesk/OS version. Afterwards, I'm unable to access the extensions catalog. The installation log shows: Rerunning the failed...
See more
Back
Top