SMTP authentication failed
Sending notification has always worked for us but suddenly stopped working. The only thing that has changed is that our ISP stopped service TLS < 1.2 with smtp SSL
n-redmine | I, [2022-05-25T17:15:06.158707 #1] INFO -- : Completed 200 OK in 1455ms (Views: 444.9ms | ActiveRecord: 928.2ms)
redmine | E, [2022-05-25T17:15:07.195104 #1] ERROR -- : Email delivery error: 535 5.7.8 Error: authentication failed:
redmine | I, [2022-05-25T17:15:07.195536 #1] INFO -- : Performed ActionMailer::DeliveryJob (Job ID: 7f01d079-8b20-4f4f-aef8-b034b54855f4) from Async(mailers) in 2505.75ms
Using openssl s_client -connect on the same host and same credentials:
220 submission10.mail.****.nl ESMTP
250-AUTH PLAIN LOGIN
235 2.7.0 Authentication successful
How can I debug or progress this issue further?
#3 Updated by Holger Just 30 days ago
- Status changed from New to Needs feedback
The authentication error you are observing there is likely unrelated to the change in TLS versions. If the TLS change would be the cause, you would get a transport-level exception, rather than an SMTP error code.
As such, it's more likely that you are using a wrong username or password in your Redmine configuration. You may verify this by checking the generated
configuration.yml file within your running docker instance.
Please note that the Redmine docker image at https://hub.docker.com/_/redmine is not maintained by the Redmine project but the docker community. As such, configuration issues with this docker image can likely not be addressed by the Redmine project but must be handled by the (external) team maintaining the Redmine image at docker, e.g. at https://github.com/docker-library/redmine/issues.
(With that being said: in the
openssl s_client session you have posted in your issue description, you have apparently posted your actual base64 encoded password. As this password is now publicly visible, you should consider it leaked and I strongly encourage you to change it as soon as possible.)