[GH-ISSUE #1892] SMTP Client error: internal client error: No compatible authentication mechanism was found #1097

Closed
opened 2026-03-03 02:06:14 +03:00 by kerem · 6 comments
Owner

Originally created by @belerovon on GitHub (Aug 11, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1892

I use an Postfix SMTP Relay host for outgoing mails - also I configured valuewarden to use this host in the same way.
The SMTP Relay Host accept my private networks and has no authentication enabled.

Now when I try to send mails via valuewarden I got the following error:
[2021-08-11 10:34:59.896][vaultwarden::mail][ERROR] SMTP Client error: internal client error: No compatible authentication mechanism was found

Some version before Bitwarden_rs works fine with this host.

Originally created by @belerovon on GitHub (Aug 11, 2021). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1892 I use an Postfix SMTP Relay host for outgoing mails - also I configured valuewarden to use this host in the same way. The SMTP Relay Host accept my private networks and has no authentication enabled. Now when I try to send mails via valuewarden I got the following error: [2021-08-11 10:34:59.896][vaultwarden::mail][ERROR] SMTP Client error: internal client error: No compatible authentication mechanism was found Some version before Bitwarden_rs works fine with this host.
kerem closed this issue 2026-03-03 02:06:15 +03:00
Author
Owner

@belerovon commented on GitHub (Aug 11, 2021):

Wrong parameter in docker-compose

<!-- gh-comment-id:896702573 --> @belerovon commented on GitHub (Aug 11, 2021): Wrong parameter in docker-compose
Author
Owner

@melbv commented on GitHub (Sep 21, 2021):

Just found this and i have the same issue - could you specify what you corrected in the docker-compose?
Many thanks in advance

<!-- gh-comment-id:924212906 --> @melbv commented on GitHub (Sep 21, 2021): Just found this and i have the same issue - could you specify what you corrected in the docker-compose? Many thanks in advance
Author
Owner

@BlackDex commented on GitHub (Sep 21, 2021):

normally this means a wrong port, or not using ssl/tls when that is needed.
You can enable SMTP_DEBUG=true for a short time while testing and see what the output is.

<!-- gh-comment-id:924218950 --> @BlackDex commented on GitHub (Sep 21, 2021): normally this means a wrong port, or not using ssl/tls when that is needed. You can enable SMTP_DEBUG=true for a short time while testing and see what the output is.
Author
Owner

@melbv commented on GitHub (Sep 21, 2021):

Hi Mathijs
Thanks for the reply. I was testing the setup w/o TLS/SSL on port 25 to avoid those but will try with the encryption to see if it changes anything
21 Sep 2021, 18:49 by @.***:

normally this means a wrong port, or not using ssl/tls when that is needed.
You can enable SMTP_DEBUG=true for a short time while testing and see what the output is.


You are receiving this because you commented.
Reply to this email directly, > view it on GitHub https://github.com/dani-garcia/vaultwarden/issues/1892#issuecomment-924218950> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/AVIFVNRCPOBM74RBJESCGJDUDDAS3ANCNFSM5B54MU2A> .
Triage notifications on the go with GitHub Mobile for > iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or > Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .

<!-- gh-comment-id:924230357 --> @melbv commented on GitHub (Sep 21, 2021): Hi Mathijs Thanks for the reply. I was testing the setup w/o TLS/SSL on port 25 to avoid those but will try with the encryption to see if it changes anything 21 Sep 2021, 18:49 by ***@***.***: > > > > > > > normally this means a wrong port, or not using ssl/tls when that is needed. > You can enable SMTP_DEBUG=true for a short time while testing and see what the output is. > > > > > > > — > You are receiving this because you commented. > Reply to this email directly, > view it on GitHub <https://github.com/dani-garcia/vaultwarden/issues/1892#issuecomment-924218950>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AVIFVNRCPOBM74RBJESCGJDUDDAS3ANCNFSM5B54MU2A>> . > Triage notifications on the go with GitHub Mobile for > iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>> or > Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>> . > > > >
Author
Owner

@BlackDex commented on GitHub (Sep 21, 2021):

Normally port 25 doesn't allow login, only 587 or 465 allow login and sending email.
Port 25 is only used for receiving e-mail by the final endpoint.

<!-- gh-comment-id:924239057 --> @BlackDex commented on GitHub (Sep 21, 2021): Normally port 25 doesn't allow login, only 587 or 465 allow login and sending email. Port 25 is only used for receiving e-mail by the final endpoint.
Author
Owner

@melbv commented on GitHub (Sep 21, 2021):

Tbh, 25 is perfectly fine for relaying btw an app & a mta on the same server - which i do on another machine where i run nextcloud with postfix (no docker install).
Having docker containers on this machine complicates a little the declarations and i thought i could have learnt something from the set up to implement! Ill keep looking then...

21 Sep 2021, 19:15 by @.***:

Normally port 25 doesn't allow login, only 587 or 465 allow login and sending email.
Port 25 is only used for receiving e-mail by the final endpoint.


You are receiving this because you commented.
Reply to this email directly, > view it on GitHub https://github.com/dani-garcia/vaultwarden/issues/1892#issuecomment-924239057> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/AVIFVNVW63WNNFYT3V5LNMLUDDDTVANCNFSM5B54MU2A> .
Triage notifications on the go with GitHub Mobile for > iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or > Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .

<!-- gh-comment-id:924304411 --> @melbv commented on GitHub (Sep 21, 2021): Tbh, 25 is perfectly fine for relaying btw an app & a mta on the same server - which i do on another machine where i run nextcloud with postfix (no docker install). Having docker containers on this machine complicates a little the declarations and i thought i could have learnt something from the set up to implement! Ill keep looking then... 21 Sep 2021, 19:15 by ***@***.***: > > > > > > > Normally port 25 doesn't allow login, only 587 or 465 allow login and sending email. > Port 25 is only used for receiving e-mail by the final endpoint. > > > > > > > — > You are receiving this because you commented. > Reply to this email directly, > view it on GitHub <https://github.com/dani-garcia/vaultwarden/issues/1892#issuecomment-924239057>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AVIFVNVW63WNNFYT3V5LNMLUDDDTVANCNFSM5B54MU2A>> . > Triage notifications on the go with GitHub Mobile for > iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>> or > Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>> . > > > >
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vaultwarden#1097
No description provided.