ERROR: 'SmarterMail 100.x +' CreateAccount
System.Exception: Could not create mailbox ---> System.AggregateException: One or more errors occurred. ---> System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request).
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at SolidCP.Providers.Mail.SmarterMail100.<GetDomainAccessToken>d__21.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SolidCP.Providers.Mail.SmarterMail100.<ExecDomainPostCommand>d__26.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at SolidCP.Providers.Mail.SmarterMail100.CreateAccount(MailAccount mailbox)
--- End of inner exception stack trace ---
at SolidCP.Providers.Mail.SmarterMail100.CreateAccount(MailAccount mailbox)
at SolidCP.Server.MailServer.CreateAccount(MailAccount account)

updated SM to latest build 9581

Anyone facing such issue

Thanks

Thanks

SELECT PropertyName, PropertyValue FROM ServiceProperties
WHERE ServiceID = YOUR_SERVICE_ID AND PropertyName = 'serviceurl'

It should be just `https://your-mail-host` and not `https://your-mail-host/services/`

2. Confirm the service items (mail domains) are actually linked to the SM100 service and not still pointing to an old SM10 service:

SELECT si.ItemID, si.ItemName, si.ServiceID, s.ProviderID, p.DisplayName
FROM ServiceItems si
JOIN Services s ON si.ServiceID = s.ServiceID
JOIN Providers p ON s.ProviderID = p.ProviderID
WHERE si.ItemTypeID IN (SELECT ItemTypeID FROM ServiceItemTypes WHERE DisplayName LIKE '%Mail Domain%')

If any mail domains are still linked to a service with ProviderID 66 (SM10), that's the problem — they need to be moved to the SM100 service.

Interesting that SmarterTools confirmed a known bug. Would be good to know if it's specifically about the removed `svcMailServerAdmin.asmx` endpoint or something else in the REST API...

I am already on SM100 and above steps already in place

also tried with new admin id without 2FA and with / without IP restriction but same issue 
Your first line - The root cause is that Build 9540 removed the SOAP endpoint `svcMailServerAdmin.asmx can be the cause 

Also response from SM - about some known bug and expecting fix soon.

Let me know if you are able to resolve the issue at your end.

Thanks

Invoke-WebRequest -Uri "https://YOUR_MAIL_HOST/services/svcMailServerAdmin.asmx" -UseBasicParsing

This returns 404, while other SOAP endpoints like `svcDomainAdmin.asmx` still return 200.


The fix (requires SolidCP 1.5.1+):

1. Change the provider from SM10 (ProviderID 66) to SM100 (ProviderID 67) in SQL:

UPDATE Services SET ProviderID = 67 WHERE ServiceID = YOUR_SERVICE_ID

2. Update the service URL to remove `/services/` (SM100 uses the REST API, not SOAP) in SQL:

UPDATE ServiceProperties
SET PropertyValue = 'https://YOUR_MAIL_HOST'
WHERE ServiceID = YOUR_SERVICE_ID AND PropertyName = 'serviceurl'

Or just remove "/services/" from SmarterMail Web Services URL" in the control panel.


3. Check that the `defaultdomainhostname` property exists for the service in SQL:

SELECT PropertyName, PropertyValue FROM ServiceProperties
WHERE ServiceID = YOUR_SERVICE_ID AND PropertyName = 'defaultdomainhostname'

If it doesn't exist, insert it:

INSERT INTO ServiceProperties (ServiceID, PropertyName, PropertyValue)
VALUES (YOUR_SERVICE_ID, 'defaultdomainhostname', 'mail.')

You can confirm the REST API works before making changes:

Invoke-WebRequest -Uri "https://YOUR_MAIL_HOST/api/v1/auth/authenticate-user" -Method POST -ContentType "application/json" -Body '{"username":"admin","password":"test"}' -UseBasicParsing

If it returns JSON with `resultCode: 401`, the REST API is working.


Whitelisting IPs didn't help because the issue is not about IP restrictions - it's about the SOAP endpoint being completely removed.


Hope this helps!

can you kindly update on this

Thanks

Build 9518 (Jan 22, 2026)