BUG: When creating a new mail account in SCP, it creates a blank signature on SM. Having a blank signature can sometimes mess with the HTML formatting of the message.
Expected Behavior: Only create a signature on SM when it is created in SCP.
This has now been fixed in the new version. Signature is only created when text has been entered.
Just discovered that if you click Save for the mail account a second time in SCP, it will create a blank signature.
Thanks again, Trevor. I believe that two important features for the new version are: displaying the disk space usage of the email account and an option where the user can add trusted senders to the domain.
@jack These are feature requests and not the core functionality or bugs of the Smartermail providers version 10 and 100. I don't know if Trevor or Marco are willing to do custom development at this point but I would also love to sponser some features such as enabling Chat rooms in the Mail Groups.
@jack As Chris has said we are running out of time for this work. Please can you make a feature request at https://github.com/FuseCP/SolidCP/issues (It should be one request per issue)
We can do paid devlopment but it depends on how busy we are at the time (Best to send a ticket if your looking for a quote) and if we can freeup the time needed to fully work on the code.
As you can see in 12h yesterday we was able to push through a bunch of bugs and hopefully have the basics of Smartermail100 provider working for the next release but that time is limited and i dont think i will be able to free up alot more time to fix any other issues before the next release.
Edit for clarification: We do paid development but not custom development. We require all dev work is 100% pushed to the project source and for use by other users.
BUG: When creating a signature in SCP, it does not format the spacing correctly on SM.
Expected Behavior: Signatures created in SCP should look the same in SM.
@enguard Trevor has added a visual editor for the signatures in the Github repo, however as this requires a portal update you will not be able to easily update with a single dll replacement etc.
It should fix this formatting issue too (but most likely most easy to wait for the 1.5.0 release in a little over a week for updating scp to make this work).
BUG: SCP does not pull all the Domain Defaults from SM
Expected Behavior: SCP should create the domain on SM with the Domain Defaults
This affects the Autodiscover features, as it will give the mail client the wrong hostname to auto-configure.
For this i wont set the host and it should pickup the default as i think thats best anyway
Looks like its not possible to just leave it blank. When i check how to call the domaindefaults i dont see any API Call. Not sure if you can rush it through with Smartermail to find the call? I did find user-defaults but no domain.
Trying to not set the host also doesnt help as its a required field
Regards,
Trevor
@trobinson OK I see that you set it to mail.domain.com, which is an acceptable solution as most people will set it to that. Because we host many domains on a server, we just have one hostname for all domains. They are not individually set per domain. We can manually change it if you don't see an API call to pull the hostname from Domain Defaults.
@enguard I was thinking would it be better to have a provider setting to set Hostname?
I presume this is like exchange where the domain needs to have SSL set and you can use the same host domain for multiple mail domains?
@trobinson agreed. The provider can change the host name to whatever they want. Having it set mail.domain.com as default on domain creation is a good start. We can leave this alone.
That setting was from the old SM10 provider as it was we copied over the provider page but does it make sense and if yes how?
If the plan has 10 users then we should set 10 users. I dont see a reason to go over that figure.
@trobinson It does ignore the SCP Plan limit defaults. The Unlimited space and Unlimited Users it creates for the domain is not a big deal, we can manually change those.
@trobinson We discovered today that setting the disk limit to 0 is actually not unlimited and breaks the domain. Users are unable to receive email and senders get a bounce:
Remote Server returned: 'The domain size limit has been exceeded'
This gets reset to 0 each time we pause and un-pause the account.
We are testing the SM100 Provider on a production server this morning and unable to create mail accounts. It is creating these errors in the Event Log, any idea what we are missing here?
[11/25/2024 7:37:56 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/25/2024 7:37:56 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)
[11/25/2024 7:54:05 AM] ERROR: 'SmarterMail 100.x +' DomainAliasExists
System.Exception: Could not get the list of mail domain aliases ---> System.NullReferenceException: Object reference not set to an instance of an object.
at SolidCP.Providers.Mail.SmarterMail100.GetDomainAliases(String domainName)
--- End of inner exception stack trace ---
at SolidCP.Providers.Mail.SmarterMail100.GetDomainAliases(String domainName)
at SolidCP.Server.MailServer.GetDomainAliases(String domainName)
@enguard Sounds like maybe a API issue. If you enable verbose logging on the SCPServer does it write a info event starting with ExecDomainGetCommand?
