You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a drop down list "Encryption Method" SSL/TLS or None (maybe automatically adjust the port, 25, 465 or 587)
Add a checkbox "The mail server requires authentication" which would then show/hide both username and password fields
Example of another mail client:
🎤 Pitch / Usecases
Currently the mail client (SMTP configuration for notifications) is not flexible.
Only encrypted and authenticated smtp is supported, which poses certificates challenges in some environment, where encryption nor authentication isn't required, for example when both devtron and the email server run in the same network.
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
Hey @u72z we're working on this request. You can expect this with our next release. If this one is a blocker for your org, let's connect on discord (my username abhibhaw) and I could try to see how quickly we can unblock you.
Hey @u72z we're working on this request. You can expect this with our next release. If this one is a blocker for your org, let's connect on discord (my username abhibhaw) and I could try to see how quickly we can unblock you.
🔖 Feature description
Add a drop down list "Encryption Method" SSL/TLS or None (maybe automatically adjust the port, 25, 465 or 587)
Add a checkbox "The mail server requires authentication" which would then show/hide both username and password fields
Example of another mail client:
🎤 Pitch / Usecases
Currently the mail client (SMTP configuration for notifications) is not flexible.
Only encrypted and authenticated smtp is supported, which poses certificates challenges in some environment, where encryption nor authentication isn't required, for example when both devtron and the email server run in the same network.
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
AB#9136
The text was updated successfully, but these errors were encountered: