• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Email encoding after upgrade to 18.0.65

The case is still under investigation. The issue is inconsistent and our team has several theories on what exactly is causing it. If you haven't already please consider disabling “Fix incorrectly set sender for outgoing mail“ and/or "Turn on limitations on outgoing email messages" until we can bring more clarity.


I will discuss this matter with our team on Wednesday and I will provide more details on the current release scheme and our future release plans.

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.
 
Back
Top