Do you have all these options enabled on the server?
@enguard Yes, I have them enabled, I have also tried disabling the options but the same error occurs in solidcp
Thank you
@jack I assume you are not putting the user name into the password right? Give me an example of a password you are putting in so I can try to replicate it here.
Hello, can someone send full list not working smatermail, so my team can look at getting fix done
I have requested this from solidcp but had reply about
If some can send me full list not working be very good
@macintoshelectronics As far as i am aware we did reply any and all tickets you have submitted (and communication stopped at your end).
As mentioned in the tickets: we do not have any detailed information about the issues (pending community feedback).
All information we have is in github (thats where all known bugs and issues are listed of what we are aware of):
https://github.com/FuseCP/SolidCP/issues/142
https://github.com/FuseCP/SolidCP/issues/60
@macintoshelectronics Are you a developer? We are looking for and willing to pay someone to get this fixed and also some customization as well.
Yes I have team of dev can fix the issues
If someone forwarded full list bugs not working
With solidcp not working with current build smartermail
Email me karl@macintoshelectronics.com
or whatapp me +447754400465
@macintoshelectronics sorry just saw this now. This forum didn't send me an email notification of your reply. I just sent you an email.
If anyone is still working on this - I'll be happy to chip in if they can add MAPI and EAS support.
Hello,
Did you guys manage to make any progress?
We are planning a new stable release 1.5.0 at 02-12-2024 which would be great if we can include any bug fixes for SM.
Regards,
Marco
Hi, no we didn't make any progress, spent over 10 months looking some to work on SolidCP, no wanted to work on it even paying good money for it we gave up in the end now looking something else
We even asked you forward contact details or put us in touch dev you have worked with in the past
@macintoshelectronics It's generally hard for "one off" devs to work on scp as it has a steep learning curve (it's also using framework which is really phased out, including by our selfs).
We don't really have any dev's to recommend for such projects outside of our own paid development (with a key rule: paid or not - anything we make goes back into the opensource project, we do not make any closed or private codes).
We do not really work with freelancers, most dev is done by our selfs or our partners (including the updated sm provider, which worked untill sm changed some api codes again without documenting from what i could gather).
Others who work or have worked on the project can be found in Github.
