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

Search results

  1. grAlex

    Resolved mailmng-server returns "bad lexical cast" error

    Well, my postfix config was missing message_size_limit = 102400000 After I've added the line into /etc/postfix/main.cf the error has gone. Seems the issue is now solved. We're using custom setup for Postfix with multiple instances. Regards, Alex
  2. grAlex

    Resolved mailmng-server returns "bad lexical cast" error

    Hello Burnley, Thanks for your reply. Not too sure what you mean, but submission is fine: tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 1391/master and the error persists. And even if I disable submission in master.cf the error persists. Is there anything...
  3. grAlex

    Resolved mailmng-server returns "bad lexical cast" error

    Hello, Plesk version: 17.5.3 CentOS 7 1705170317.16 I've got a weird error and I hope you can help me with it: [root@server bin]# ./mailmng-server --get-mailbox-size-limit Fatal error: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast>...
Back
Top