-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SMTP email notification auth - optional #1697
Comments
Hi, many thanks for your feedback. |
Thanks for your quick reply. It is for a project I have been working on for a large German airline. They need it yesterday ;) So the sooner it is possible the better for me. Thanks again. |
Got it, I'll let you know once it will be done |
Implemented in #1698 |
Thanks. Are the above listed variables now configurable and under the same naming convention as listed? |
Renamed: Also about notifications.receivers.emails.protocol values: 1. smtp (Simple Mail Transfer Protocol) 2. smtps (SMTP over SSL) 3. imap (Internet Message Access Protocol) 4. imaps (IMAP over SSL) 5. pop3 (Post Office Protocol 3) 6. pop3s (POP3 over SSL) P.S. I'll close this issue once we will publish new release. I think it will be in the next couple of days |
Beautiful. Thanks for the quick turn around |
Is your proposal related to a problem?
The problem is that email notifications if the smtp server does not require TLS auth.
Describe the solution you'd like
Make these config variables configurable:
"mail.transport.protocol"
"mail.smtp.auth"
"mail.smtp.starttls.enable"
and this should in turn be optional
notifications.receivers.email.password
Describe alternatives you've considered
I have attempted to overwrite these in the config and only get errors:
Mail server connection failed. Failed messages: jakarta.mail.MessagingException: Could not convert socket to TLS;
I tried to pass placeholders for the receivers email password. Sadly nothing has worked
Additional context
I am available in your slack under Samuel McGuire. Please feel free to get in touch.
(Write your answer here.)
The text was updated successfully, but these errors were encountered: