• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Very very Weird Plesk setting

nitaish

New Pleskian
I found a very weird setting in Plesk for email forwarding. We have Plesk 10.4.4 on a few Windows hosting server with Smartermail lite editions. When we set email forwarding for an email account from Plesk, instead of directly forwarding it to the destination inside Smartermail, it sets the forwarding to a random user which in turn is created as an alias and the destintation email account is added as a destination of the alias. This is unnecessarily increasing the mail delivery time and also the emails fail to deliver in many cases. Can Parallels explain the reason to make a simple setting so complex?
 
According to Plesk devs, in SmarterMail, you can forward email to quite limited number of recipients (maybe even to only one). Plesk has no limit for number of recipients on forwarding.
Due to this, Plesk creates temporary mail alias that is not limited by number of recipients and forwards the email to this alias. So, this is some kind of development tricks to workaround specific behavior of the certain mail server.
 
Back
Top