Facebook
Twitter-
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.
Resolved Email encoding after upgrade to 18.0.65
TorbHo
Regular Pleskian
There is an update available now. See:
computermobil
New Pleskian
That sounds good. Anyone installed yet?
it works for me.
TorbHo
Regular Pleskian
Yes, it seems to work now.
Is there any news on the release scheme and the future release plans?
Apologies for the delay, Maarten. I didn't have a chance to discuss that with the team in charge last week, but we did this week. The primary reason for Plesk to switch and stick to the current release scheme for all that time is due to the aim to deliver fast to major part of our audience in all possible meanings: stability, security, new scenarios. We understand that regardless of the utmost efforts we put in pre-release tests in order to ensure a stable build occasionally issues do arise and could result in unpleasant experience for some users. Still, it is hard or even impossible to do so with long-term release tears. For example security: panel relies on huge amount of third-party software (as we actually configure it). security updates and new versions are released very often. With old release tiers we will not be able to adopt it and deliver. The same for stability: software vendors release new versions with new functions and new problems - we need to adopt and deliver our product for this changes fast. The feedback (from all users) on how the process could be improved was forwarded to the corresponding team. It will be definitely taken into account and implemented in the feature if they decide the long-term impact of it will bring positives.