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

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