Outbound email settings being overwritten when app is restarted

[ccfu]

@nebulon Thanks for the explanation. Then I can see why it is good to write the configuration on a restart but I would then like to request the flag to maintain settings in the app also be added to Espo.

[nebulon]

Yes, I have added to my list.

[ccfu]

@nebulon Thank you!

[ccfu]

@nebulon Any ETA on this? The latest app update once again overwrote the mail settings and because the port is still being saved as 2,525, the default settings don't work either.

[girish]

@ccfu I guess we have two options . We report issue upstream and can also submit a fix upstream to fix the port separator issue. Alternately, we have to make email configuration optional in the Cloudron package. We prefer the former since the larger project will benefit . What do you think?

[ccfu]

@girish I would also be happy with the former. I suspect most people have 2- or 3-digit port numbers so this has not been an issue for the developers up to now.

[imc67]

Strange that you experienced issues with the port number, ours (2 EspoCRM instances) never had any issue and the port number is automatically set at 2.525

[ccfu]

@imc67 Interesting it works for you. Maybe I need to revisit this this. Perhaps it makes a difference that in your case it is 2.525 and in ours 2,525 because of our settings, but either would be invalid port numbers.

[imc67]

@ccfu in the config.php it shows as:

'smtpPort' => '2525',

so I guess it's just a GUI "thing"?

[girish]

@ccfu yes, can you please test again and let us know?

[nebulon]

I have just hit this problem as well on a fresh installation while looking at customer one. Not yet clear what the issue is but will keep this updated.

[nebulon]

https://github.com/espocrm/espocrm/issues/3010 is for the UI fixes, but seems like upstream can't actually reproduce this...

[girish]

Looks like https://github.com/espocrm/espocrm/issues/3010 got fixed

[ccfu]

Apologies for forgetting to reply again in this thread and confirm the problem still existed. Thanks for reporting it upstream. Looks like it could in fact be reproduced and has been fixed.

The group account solution is what I had been using up to now but this had to be reset every time there was an update or the app was restarted.