mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-25 17:25:57 +03:00
[GH-ISSUE #4992] about email 2FA error:SMTP error: response error: error Tag at: #2039
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#2039
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 @CJSen on GitHub (Sep 25, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4992
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, SHOW_PASSWORD_HINT, ADMIN_TOKEN, SMTP_HOST, SMTP_SECURITY, SMTP_PORT, SMTP_FROM, SMTP_USERNAME, SMTP_PASSWORD
Vaultwarden Build Version
v1.32.0-040e2a7b
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
nginx 1.27.0
Host/Server Operating System
Linux
Operating System Version
ubuntu 22.04
Clients
Browser Extension, Desktop
Client Version
No response
Steps To Reproduce
Expected Result
I declare in advance that I used the beta version of the code to test whether it was a real issue, and this is also the issue in the official version.
I have configured the SMTP server (QQ email) on the admin page
Click on test, an error message appears as shown below, but the test email received the email


Change the SMTP service provider, email sending is normal, and the software is working properly.
There was no problem in using it before. So I initially think that the qq mailbox may have made some changes to the return value or other aspects, resulting in an abnormality in the code?
Actual Result
like Expected Result
Logs
Screenshots or Videos
No response
Additional Context
No response
@BlackDex commented on GitHub (Sep 25, 2024):
Enable
SMTP_DEBUG=trueand see what it reports.I do not think we can change anything to solve this.
@CJSen commented on GitHub (Sep 25, 2024):
thank you answer,this is my log with SMTP_DEBUG=true. I hidden my email address.
@BlackDex commented on GitHub (Sep 25, 2024):
If anything, then we need to check with lettre i think @paolobarbolini ?
@BlackDex commented on GitHub (Sep 26, 2024):
Looking at it again, i see the following
Do you maybe have changed the email templates?
@CJSen commented on GitHub (Sep 26, 2024):
Sorry bro,I don't know why it shows no network,but it does have a network.
As I said, although it reported an error when I used the QQ mailbox, my destination mailbox did receive the relevant email. When I switch to another mailbox service(such as @163.com mailbox), there is no error. Everything is fine.
@LTI-Lennox commented on GitHub (Sep 26, 2024):
I have the same problem
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: ADMIN_TOKEN
Logs
Screenshots
@CJSen commented on GitHub (Sep 26, 2024):
@LTI-Lennox Hey bro, is your smtp server also QQ mailbox?
@LTI-Lennox commented on GitHub (Sep 26, 2024):
@CJSen commented on GitHub (Sep 26, 2024):
@LTI-Lennox A touch of the same, me too. A temporary solution:
@BlackDex commented on GitHub (Sep 26, 2024):
I Would say to report this to qq actually. This seems an issue with the implementation of there SMTP server.
It's a bad idea to add exceptions for specific errors like this into our code.
You could try to add a custom mail-proxy in between maybe? But good chance it also might generate errors.
Since this is really something coming from the remote mail server, and not something which is a specific bug on the Vaultwarden side, I'm going to move this to a discussion.