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

Issue Subfolder "domains" is added to mail path (Plesk 18.0.21 and Smartermail 10.x)

When creating a new subscription, or adding a domain to an existing one, a subfolder "Domains" is created in the existing mail path, i.e. if the mail path is "d:\SmarterMail\Domains" the domains will be created in "d:\SmarterMail\Domains\Domains" folder.

It does not stop there. After a restart if the SmarterMail Service, a check will be done on the current domain folder. If there is an "Domains" subfolder in the existing folder, the settings (settings.json in the SmarterMail\Services folder) will be updated:

"path_smartermail_root": "D:\\SmarterMail\\Domains\\" is updated to "path_smartermail_root": "D:\\SmarterMail\\Domains\\Domains\\"

And from that moment on if you create a new domain, a sub folder will be created in the existing (new) folder. And so on and on.... I ended up with 5 levels of Domains folders.

I noticed the value of Mail_path (servicenodeenvironment table in the psa database) is updated as well. Does it check SmarterMail or the settings.json file?

My first guess would be that the creation of the domains subfolder is hardcoded somewhere.

This occurs on both my (current) Windows 2016 and my (new) Windows 2019 Server.

I hope there is a quick fix...

Note: SmarterMail version is 100.0.7242
 
Back
Top