[Bug]: SMTP server setup with no tls issue

[heiniha]

Error Message and Logs

Leaving the envryption field empty does not work for coolify to send the mail without starttls.
Our mailserver always receives requests including starttls.
Would like the option to choose not to use starttls, or if that already exist, then how can I configure it inside the Coolify settings menu -> transactional email -> SMTP server?

Steps to Reproduce

1. Configure smtp server settings without encryption set
2. Test send email
3. Coolify marks it as sent successfully
4. Mail server denies request with starttls

Example Repository URL

No response

Coolify Version

v4.0.0-beta.369

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04

Additional Information

No response

[pshemek]

I have issues with SMTP settings as well. Actually, I found that Coolify's notification test displays success no matter what I configure system-wide (including wrong password, etc.)

Also, when I try to set different email than default one in notification test, server error occurs:
Error: Cannot update locked property: [emails]

[peaklabs-dev]

@heiniha you can set it to tls and port 465 that will always use tls, if you use 587 it will try to use STARTTLS if availabe. What is your exact issue you are having?

@pshemek This will be fixed in one of the next version and is a different issues.

[heiniha]

@peaklabs-dev well, if running in own hosted environment and having a mailrelay available, but only on port 25 (smtp) and using a anonymous solution, so basically no user or password needed and also no tls or starttls needed or possible, then coolify says the email was sent successfully, but in the mail server log I see it still tries starttls.

Basically I would have thought that a no-tls option would be correct, and perhaps a checkbox for enabling anonymous account solution.

Many companies run like this to quickly scale their environments.

[peaklabs-dev]

So you want to use SMTP with no username and password and over port 25 (so no TLS). And then you want no encryption to be used and even with port 25 Coolify still uses encryption right? Am I getting this right? I am not sure this is a good idea though because it is highly insecure no encryption and no username and password.

[andrasbacsai]

So you want to use SMTP with no username and password and over port 25 (so no TLS). And then you want no encryption to be used and even with port 25 Coolify still uses encryption right? Am I getting this right? I am not sure this is a good idea though because it is highly insecure no encryption and no username and password.

That is true. It is highly insecure, but as it is an allowed configuration, we need to support it.

@heiniha What I do not understand if you leave it empty (null), then no TLS connection should be started, am I wrong?

[heiniha]

Well I understand it is insecure, but when running self hosted and managing own network, we are able to limit its accessibility into where the traffic flows, hence we're using smtp port 25 relay, without user/pass and no tls support.

If I choose to not set anything in the encryption field, I still see it using starttls on mailserver and no-tls in the field is the same, still see starttls on mailserver.

[heiniha]

Hi,

Thanks this is working now in the latest 380 release 😃