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

[11.0.9 #13 CentOS 6.3 64bit] mailmng failed: Empty error message from utility

burnleyvic

Regular Pleskian
This bug isn't replicating on Plesk 10.4.4.
- Create a subscription domain.com, then select it and go to Mail.
- Create a mail address 'user@domain.com' with no password set
- Click on the mail address to edit its properties. Rename user as user1 and set a password. Click on OK to save the changes. Plesk will display:
"Error: Unable to update the mail account properties:mailmng failed: Empty error message from utility."
I can't reproduce it if:
- I only rename the account, not setting any password
- I only set the password and leave the account name unchanged
What's worse is that the mail directory is actually renamed as 'user1', but in the database 'user' is still used.
 
Thanks. I have reproduced this issue on our test Plesk installation and submitted corresponding request to developers.
I hope it will be fixed soon.
 
Back
Top