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

Receiving error on creating a specific mail name

G

grfecom

Guest
I would be so happy if someone can give me help about following unusual error message:

Error: Unable to update the mail name properties:mailmng failed: MEAOPO.Mailbox.AddMailbox failed for name=2ndigf and domain igforum.net [igforum.net]

This happens when I simply want to create a new mailbox under that domain. I could create any other names except that one!

What is the meaning of that message? I could not find any help or hints on Plesk's manuals.

Thanks!
 
I fixed the problem!

Open the MailEnable console here: C:\Program Files\SWsoft\Plesk\Mail Servers\Mail Enable\Bin\MailEnable.msc

Browse the domain has the issue. You will see the duplicated value for the same mail name ubder the mailboxes. Simply remove it and you are good to go!
 
Hi, we have the same error message using plesk9 and mailenable enterprise. when creating the account in plesk it fails with the before mentioned error. It creates the account as a disabled account with no password in mail enable tho. deleting the account from mail enabvle yields the same result in plesk. all domains on that server are having the same issue.
 
Found that the issue has somethign to do with the "prevent simple passwords" option in mail enable. when it is turned off, the problem goes away. Is there a similar option in the plesk mail setting somewhere that does the same thing? im pretty sure plesk throws a fit when you change a plesk configurable option from the third party add-on instead of from the plesk panel.
 
Back
Top