BUG: Creation of mail account creates an Unlimited sized mailbox in SCP and mailbox size of 0.09765625 instead of plan mailbox size setting 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
BUG: Creation of mail account creates an Unlimited sized mailbox in SCP and mailbox size of 0.09765625 instead of plan mailbox size setting 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
Fixed with commit https://github.com/FuseCP/SolidCP/commit/f05d3bd83f95defbf6de1e2f392d4af7584838ae
Tested with SmarterMail Free 100.0.9088.25586 (Nov 18, 2024)
BUG: First and Last Name entered into SCP does not come through to SM, instead only the email address is comes through
Expected Behavior: First and Last Name should be entered into the Name field on SM
@enguard Can you please let me where there this is normally set? I can see on a new account the profile is filled, display name is set in domains but the name still shows the same.
@trobinson From what I can see it sets it in User (logged in) > Settings > Profile > Display Name
Any changes in that field will also reflect at Admin (logged in) > Domain > Accounts tab > Name column
I tested the SM10 Provider and it DOES pull any changes to the Display Name in SM above back into SCP and vice versa
Its strange because I CAN see that it DOES sets the name at User > Settings > Profile > Display Name on account creation
However, it does not show at Admin > Domain > Accounts tab > Name column
So there must be some kind of hidden bug here.
You can use the SM10 Provider, maybe that will provide a clue?
The reason why this matters is because the Outgoing Display name on the email messages is NOT showing the user's First and Last Name.
@enguard It looks like there is a error on their settings/domain/user-put API where displayname doesnt apply to this field. When updating an user does appear to fix this setting the same displayAS.
@trobinson when i clicked save in SCP a second time, it creates a blank signature. See attached. SM10 Provider correctly sets the name at all places on first creation.
I tested the SM10 Provider and it DOES NOT create a First and Last Name in the user's profile. Maybe that has something to do with it?
That should not have a effect. The API clearly has us set fullName & displayas. I would say this is a API issue as we send the same fields on a update account.
I will send it to them as i expect its working in the old API.
Regards,
Trevor
@trobinson OK hope they can track down where this is not working. This would be the final bug that needs to be ironed out before we can roll this out. Thank you!
@enguard Taken another look at this one and found that setting the Full Name does fix the issue.
BUG: Creating an autoresponder correctly creates it in SM, but shows as HTML back in SCP
Expected Behavior: Autoresponder should show as text in SCP instead of HTML
This has been fixed and will be inclded in the next release. It does require a portal update. I have also included signature in the html editor also
BUG: Cannot create an autoresponder for an existing account
Expected Behavior: Be able to create an autoresponder in SCP for an existing account
This appears to be working now but may have been fixed by a previous bug as we redid the API calls
BUG: Cannot create an forwarding for an existing account
Expected Behavior: Be able to create an forwarding in SCP for an existing account
@enguard This is working. The one thing i noticed is you have to enable automated fording per domain. Do you know if this was autoenabled on SM10?
@trobinson Confirming that the SM10 Provider DOES automatically toggle ON the Automated Forwarding option in Domain settings when you enter a forwarding address in SCP.
And confirmed that you HAVE TO manually toggle ON the Automated Forwarding option in Domain settings for the SM100 Provider to work
Is it possible for the API to toggle ON the Keep original sender and recipients when forwarded ?
Automated Forwarding is now set when the domain is created.
The option for keep orignal sender appears to be auto enabled in Smartermail. If your still having the problem i will log it as a feature request in github for future versions as we should make this a option to be set in the panel (It can lead to bad ip reputation, spf fail etc if the forwarding address is external).
@trobinson Confirmed creation of new domain toggles Automated Forwarding ON, which also correctly enables forwarding.
I can also confirm Keep original sender and recipients when forwarded is toggled ON for a new mail account. But for existing mail accounts that do not have that toggled ON, it stays toggled OFF when forwarding is set in SCP.
Added this as a feature request for future versions https://github.com/FuseCP/SolidCP/issues/203
