Build 9560 (Mar 5, 2026) - Breaks Plesk integration

Problem reported by Chris Danks - 3/9/2026 at 6:57 AM

Being Fixed

Hello

All of our plesk servers are unable to login to smartermail.

We use the "remote smartermail" so it uses the SM API. Plesk now also shows "unconfigured" on Remote Smartermail on server components section with no way for us to fix.

error:

Error: Unable to update the mail account properties: mailmng failed: SmarterMail version is undefined: Login failure: Missing auth
at Unable to get SmarterMail version by REST API(SMProvider::getInstance line 71)
There was an error communicating with the endpoint at 'https://REDACTED:443/Services/svcProductInfo.asmx'.
An error occurred at row 2, column 164 (0xA4) when the XML reader is processing the input source.
A start element with the name 'Envelope' and namespace 'http://www.w3.org/2003/05/soap-envelope' was expected.
A start element with the name 'Envelope' and namespace 'http://schemas.xmlsoap.org/soap/envelope/' was found, but not expected.. Technical information: SOAP ERROR: GetProductInfo() failed. Error code 0x803d0000.
at (WebService::Error::checkResult line 106)
at Unable to get SmarterMail version by SOAP API(SMProvider::getInstance line 85)
at (SMProvider::getInstance line 92)
at getMailMngProviderInstance()(mailmng::imailmngprovider::load line 500)
at (mailmng::imailmngprovider::load line 502)
at load(C:\Program Files (x86)\Plesk\admin\bin\smremoteprovider.dll)(mailmng::imailmngprovider::load line 505)
at Unable to load mail provider(mailmng::imailmngprovider::load line 520)
at get_provider()(mailmngimpl::get_provider line 1513)
at Unable to execute console command: '--add-mailname'(vconsoleapp::start line 95)
at Unable to execute command: '"C:\Program Files (x86)\Plesk\admin\bin\mailmng" --add-mailname "--domain-name=redacted.com" "--mailname=info" "--password=*"'(vconsoleapp::run line 117)
(Error code 1)

8 Replies

Reply to Thread

Sébastien Riccio Replied

3/9/2026 at 10:04 AM

I guess plesk, or the provider of the Smartermail module for plesk, needs to update their plugin so it works with latest builds.

You should contact plesk about this.

According to the error it seems that the module tries to determine the SmarterMail version automatically, using some API endpoint on the SmarterMail server that is now probably not accessible anymore.

Sébastien Riccio System & Network Admin https://swisscenter.com

Martin Blanchette Replied

3/9/2026 at 1:36 PM

On one hand, SmarterMail is telling administrators that updates must be applied quickly because older versions may contain security vulnerabilities.

On the other hand, some of these updates end up breaking important features.

Considering that Plesk has a large number of SmarterMail users — and that SmarterMail is directly integrated into their product offering — these updates should at least be tested with major partner platforms before being released.

At the very least, Plesk should be notified about potential compatibility issues prior to the public release of an update.

Tony Scholz Replied

3/10/2026 at 7:55 AM

Employee Post

Hello,

We are aware of some issues with Plesk integration with some of the new security changes and are looking into it. Thank you.

Tony Scholz Lead Network/System Administrator SmarterTools Inc. www.smartertools.com

J. LaDow Replied

3/10/2026 at 8:08 AM

The only real issue is lack of communicating breaking changes in release notes.

Plesk (and others) is/are responsible for their own integrations - but from a developer standpoint - having to guess and wonder what changed between releases is a time-consuming venture that can be avoided.

This still goes back to a continuing issue where changes to the API and other parts of the software are NOT clearly documented - and occurring WITHOUT WARNING...

Not withstanding the licensing costs - it is becoming increasingly more expensive to host SmarterMail due to continued changes and bugs that raise costs related to manpower and time-consumed to mitigate - when simply documenting and staging changes (as in COMING IN THE NEXT BUILD - BREAKING API CHANGES) could solve so many problems before they hit.

MailEnable survivor / convert --

Richard Laliberte Replied

3/10/2026 at 10:08 AM

If Sébastien is right, than build 9511 specifically stated that "Changed: About/checkup page now restricted to authorized (local network) IPs." At that time, if Plesk is using the API to get version information, they probably should have inquired or commented out that feature. I've worked with a large number of software over the years, opens source and not, and this is definitely not unique to Smartermail... Many software vendors actually have an entire 2nd paid tier for "Developer Platform" where all this would be found.

I also don't think it's a great idea to scream on a release page that "oo btw, we are changing this item for security reasons in an upcoming release" is a great idea... If anything maybe SM should have a specific communication stream just for developers like Plesk that are confirmed developers that can be trusted with secure information ahead of time via NDA's and such so they can be ready when a new fix is released?