Using SuiteCRM 8.2.3 I am unable to save SSL as a setting within the Admin>Email Settings>Enable SMTP over SSL or TLS?. Each time I select SSL, hit save, when I go back in, it is cleared. Essentially, Email will not send, if I select SSL and hit Send email, it sends successfully, but soon as I hit save, it reverts to unselected. I’m also seeing an error when I attempt to save:
Fri Feb 3 10:13:08 2023 [5740][1][FATAL] log call at: modules/EmailMan/tpls/config.tpl:459 - styleChecked is not set
Any help you can offer would be GREATLY appreciated!!
It actually seems saved in the outbound account and working. Sending a test email only fails when sending it from the Syetem email setup…Odd. Thanks for your help!!
Hey John, Thats great news!! We are attempting to Use SuiteCRM as an offering to one of our clients but I’m having an issue with the Check Inbound Email job. I explained it at:
Fri Feb 17 09:15:06 2023 [5788][1][FATAL] Couldn’t connect to mail server id: d2c84800-4735-4d1b-e19d-63e6afb4ad7f
Fri Feb 17 09:15:06 2023 [5788][1][FATAL] SCHEDULERS: could not get an IMAP connection resource for ID [ d2c84800-4735-4d1b-e19d-63e6afb4ad7f ]. Skipping mailbox [ SSGInbound ].
Hi John, thanks so much for checking into this. I can only get inbound email to work on PHP 7.4, which is an issue as that PHP version is no longer supported. 8.0 results in Imap errors, above 8.0 causes the check inbound email job to fail…
I sure agree with the really strange part, spent the majority of the day trying to figure out why the workflow wouldn’t work. Finally noticed the password and the “Enable SMTP over SSL or TLS” was lost on each workflow attempt.
Anyway, I’m using CRM7.13 and php 8.0. I’m downgrading (today) from php 8 to 7.4 today to see if it solves multiple issues (including on crm8 I’m testing also).
And please be very specific regarding which screens you used to save the email account, there are several places in SuiteCRM for these configurations and many important bug reports are unusable due to lack of detail.
The same goes for your Workflow: we should aim for reproducing the bug with the exact same thing. Thanks!