BUG: Creation of mail account creates an Unlimited sized mailbox in SCP and 0.09765625 in SM.
Expected Behavior: to create the mailbox size according to the Plan in SCP. In this example, it should have been set to 100GB
@enguard Hello Chris, What version of SmarterMail are you using for the tests? ¿0.09765625? I can't find this version
https://www.smartertools.com/smartermail/release-notes/current
@jack see my screenshots
we are on build 9056, which is the most stable version right now.
i think I’m going to start a new thread because this is getting too long. Will do after I get back from dinner.
Looks like i can only attach 1 screenshot at a time
last screenshot for bug above
@enguard Thanks for reporting this.
We are looking into this issue (and the others reported in seperate topic).
I have also fixed the attachments (so you can now upload multiple images in one post again).
Please note for actual bugs it's generally better to use Github then the forum (as thats where more devs reside including all contributors).
But for now forum will do 🙂
@m-tiggelaar I don't know how to use Github but have started a new forum topic so we can close out this thread once all bugs are fixed. My conversations with Smartertools is they haven't changed anything in the API and only work on bug fixes on their end. The current version 9056 is the most stable we have run in years. I know you guys are using a newer version than that which should be fine.
@enguard No problem like i said for now we can stick to forum (it was just future advice).
We can confirm there is actually an issue with the smartermail api which causes a big chunk of the problems.
In their doc: http://<smartermailurl>:9998/Documentation/api#/reference/SmarterMail.Web.Api.SystemAdminSettingsController/GetUser/get
The response we get:
[11/20/2024 6:36:54 PM] INFO: ExecGetCommand: URL: http://localhost:9998/api/v1/settings/sysadmin/user/01@sm100domain01.co m"> http://localhost:9998/api/v1/settings/sysadmin/user/01@sm100domain01.com
returned: {
"message": "Domain does not exist.",
"success": false
}
We have send an email to smartermail, but maybe you got some contacts there to speed things along?
Hello does it work with SmarterMail Build 9088 if so can you send any files or any build download please to us
@macintoshelectronics We only implemented a few fixes, there's an api call which appears to be broken, and still a list reported by Chris here: https://solidcp.com/forum/question/smartermail-100-x-provider-bugs/ which we are going over.
All our fixes are pushed to the master repo (when properly functioning) which requires to build the source. https://github.com/FuseCP/SolidCP/commits/master/
The fixes we make will still be part of the 1.5.0 release at 02-12-2024 tho which is just going to be a simple update of SolidCP.
Hey,
We have fixed all the bugs in the other post and was able to work out the broken API call Marco mentioned.
As a beta i am going to release the latest dll for SM100 on SolidCP 1.4.9. Most fixes will be there except the html fixes for autoresponder.
I would recommend backing up your current SM100 dll before replacing it as there might be more bugs. The download can be found at https://installer.solidcp.com/Files/1.4.9/BETA-SolidCP.Providers.Mail.SmarterMail100.zip
It will replace the file C:\SolidCP\Server asp.net v4.5\bin\SolidCP.Providers.Mail.SmarterMail100.dll (Your SolidCP Server path might be slightly different).
This was tested with SmarterMail Free 100.0.9088.25586 (Nov 18, 2024) which is currently the latest build offered.
Please give feedback here on if it fixed the bugs or not.
Regards,
Trevor
@trobinson thank you. SolidCP now works fine with the latest version of SmarterMail
@enguard Hey, I have done the fixes from the other topic and pushed the fixes to the same zip file for testing.
@enguard Should all be fixed now. Do note the new provider settings wont show until the release due to changed in web portal.
If you want to try the defaultdomainhostname you can set the property on the table [dbo].[ServiceProperties] matching your SM100 ServiceID.
@trobinson Looks like the newest DLL needs the portal update. I am getting these errors:
[11/22/2024 8:24:44 AM] ERROR: Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an object.
at SolidCP.Providers.Mail.SmarterMail100.CreateDomain(MailDomain domain)
[11/22/2024 8:24:44 AM] ERROR: 'SmarterMail 100.x +' CreateDomain
System.Exception: Could not create mail domain ---> System.NullReferenceException: Object reference not set to an instance of an object.
at SolidCP.Providers.Mail.SmarterMail100.CreateDomain(MailDomain domain)
--- End of inner exception stack trace ---
at SolidCP.Providers.Mail.SmarterMail100.CreateDomain(MailDomain domain)
at SolidCP.Server.MailServer.CreateDomain(MailDomain domain)
At this point I trust that you guys are ready to go with this SM100 Provider. So unless you want to send me the portal files to test, you should be good to go.
@enguard You could try run the following SQL from the SolidCP database to set the name (You could also set this to the one your customers need to use):
IF NOT EXISTS (Select * from [ServiceProperties] INNER JOIN Services ON ServiceProperties.ServiceID=Services.ServiceID Where Services.ProviderID = 67 AND ServiceProperties.PropertyName = N'defaultdomainhostname') BEGIN DECLARE service_cursor CURSOR FOR SELECT ServiceId FROM Services WHERE ProviderID = 67 DECLARE @ServiceID INT OPEN service_cursor FETCH NEXT FROM service_cursor INTO @ServiceID WHILE @@FETCH_STATUS = 0 BEGIN BEGIN INSERT [dbo].[ServiceProperties] ([ServiceID], [PropertyName], [PropertyValue]) VALUES (@ServiceID, N'defaultdomainhostname', N'mail.[DOMAIN_NAME]') END FETCH NEXT FROM service_cursor INTO @ServiceID END CLOSE service_cursor DEALLOCATE service_cursor END GO
I have also included these in the latest zip as a update_db.sql.
@trobinson yep, worked like a charm!
I've tested everything and we are SOLID!
Thank you for fixing this so fast and Good luck with the release!!!
@trobinson looks like when I ran this SQL, it only affected one of my servers (the latest one added). It did not update for all the other mail servers. See attached screenshot.
@enguard Are those servers using the new Provider? It will only do SM100. If they are using SM10 then they dont need this change at the moment but maybe a good idea to add it to all SM providers ready if people swap them out
Can you try the following query which will do all Smartermail versions. Please make sure to backup your database first.
-- Add defaultdomainhostname property to existing SM providers IF NOT EXISTS (Select * from [ServiceProperties] INNER JOIN Services ON ServiceProperties.ServiceID=Services.ServiceID Where Services.ProviderID = 67 AND ServiceProperties.PropertyName = N'defaultdomainhostname') BEGIN DECLARE service_cursor CURSOR FOR SELECT ServiceId FROM Services WHERE ProviderID IN (11, 14, 29, 60, 64, 65, 65, 66, 67) DECLARE @ServiceID INT OPEN service_cursor FETCH NEXT FROM service_cursor INTO @ServiceID WHILE @@FETCH_STATUS = 0 BEGIN BEGIN INSERT [dbo].[ServiceProperties] ([ServiceID], [PropertyName], [PropertyValue]) VALUES (@ServiceID, N'defaultdomainhostname', N'mail.[DOMAIN_NAME]') END FETCH NEXT FROM service_cursor INTO @ServiceID END CLOSE service_cursor DEALLOCATE service_cursor END GO
It was relatively easy to locate the ServiceID for each mail server and manually enter defaultdomainhostname and mail.[DOMAIN_NAME] into the rows inside of MSQL Mgmt Studio.
I'm not sure if your update db script was supposed to locate all mail servers and insert that row. But if that was the intention, I don't think that's working.
@enguard the newest one i just posted would do that for you. the first one i posted just did SM100 provieer (Not SM10 for example)
Thankyou for the prompt i didnt think about the moving from Smartermail 10 provider to 100.
