SolidCP no longer w...
 
Notifications
Clear all

SolidCP no longer works with Smartermail

71 Posts
8 Users
3 Likes
4,320 Views
Posts: 13
 jack
(@jack)
Active Member
Joined: 5 years ago

So we don't have the option to use the latest versions of Smartermail with SolidCP?

Reply
Posts: 13
 jack
(@jack)
Active Member
Joined: 5 years ago

Last successful test

 

------------------------------------------------------------------

SmarterMail Free 100.0.8768.31885 (Jan 3, 2024)

SolidCP 1.4.9

Provider SmarterMail 10.x +

------------------------------------------------------------------

 

The only option that does not work is importing resources (email accounts.)

 

 

 

Reply
Posts: 54
(@enguard)
Trusted Member
Joined: 6 years ago

When creating a new domain, most functions work. However, when trying to use it with existing domains / data, it does not work. In other words, things were fine in a test environment. But a lot of things broke when used in production. The short answer is no, SolidCP does not work with the latest version of Smartermail. I am now trying to negotiate with Trevor how much it would cost me to get this working for everyone. Sergio seems to have dropped the project. 

Reply
Posts: 54
(@enguard)
Trusted Member
Joined: 6 years ago

I can confirm that the original SmarterMail 10.x+ Provider (Legacy API) works with the latest SmarterMail Build 8867 as of today. I don't know when that changed on Smartertool's end but they must have re-added support for Legacy API. This will at least get us by until I can find someone to fix the SmarterMail 100.x + provider.

Reply
Posts: 13
 jack
(@jack)
Active Member
Joined: 5 years ago

Smartermail + SolidCP test

 

SmarterMail Free 100.0.8867.17559 (Apr 11, 2024)

SolidCP 1.4.9

Provider Smartermail 10+

 

Error creating email account.

System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Could not create mailbox ---> System.Exception: Password doesn't meet complexity ---> System.Exception: Password does not meet password requirements: PASSWORD_RESET_REQUIRE_NOT_USERNAME,

.......
--- End of inner exception stack trace ---

This was the bug when the old APIs were stopped by SmarterMail.

Reply
Page 9 / 10
Share: