mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #1892] SMTP Client error: internal client error: No compatible authentication mechanism was found #1097
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#1097
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@belerovon commented on GitHub (Aug 11, 2021):
Wrong parameter in docker-compose
@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
@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.
@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 @.***:
@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.
@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 @.***: