Unable to connect SmarterMail to Plesk after updating SmarterMail to 100.0.9735: component shows as Not configured

Symptoms

• SmarterMail component shows up as Not configured in Tools & Settings > Server Components after updating SmarterMail to version 100.0.9735.
• Submitting the correct SmarterMail administrator password in Plesk does not change the status.
• SmarterMail itself is running and reachable, and the administrator credentials work when logging in directly (for example, via http://localhost:9998).

• Errors similar to the following are shown when managing mail accounts and are logged in %plesk_dir%admin\logs\php_error.log:

  CONFIG_TEXT: [2026-08-28 19:53:19] 28592:6a91d91f48a2b ERR [panel.ui] Unable to update the mail account properties: mailmng failed: not a string
  at getRealDomainName(example.com, false)(SmarterMail::Local::Provider::getRealDomainName line 1332)
  at newMailName(john.doe, example.com, 0)(SmarterMail::Local::Provider::newMailName line 218)
  at Unable to execute console command: '--add-mailname'(vconsoleapp::start line 95)
  at Unable to execute command: 'D:\Plesk\admin\bin\mailmng --add-mailname "--domain-name=example.com" "--mailname=john.doe" "--password=*"'(vconsoleapp::run line 117)
  (Error code 1)

• With debug mode enabled, the component configuration command completes successfully but the component still shows as Not configured:

  CONFIG_TEXT: [2026-08-28 19:59:26] DEBUG [util_exec] Starting: defpackagemng --set-params --type=mailserver --package=smartermail --values=<parameters><parameter name="login" value="admin"/><parameter name="password" value="password"/><parameter name="port" value="9998"/></parameters>, stdin:
  [2026-08-28 19:59:30] DEBUG [util_exec] Finished in 4.303s, Error code: 0, stdout: true, stderr:

Cause

This is a Plesk bug with ID PPPM-15497, planned to be fixed in Plesk version 18.0.81.

Resolution

Update Plesk to version 18.0.81 or later once it is released.