From 8a6da8b61fa8c5464e77bdfe9f83e35cf9b22908 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?B=C3=B9i=20Minh=20=C4=90=E1=BB=A9c?= Date: Wed, 29 Oct 2025 23:26:17 +0700 Subject: [PATCH] wording, sorry --- SMTP-Configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SMTP-Configuration.md b/SMTP-Configuration.md index f16d76c..6a506f5 100644 --- a/SMTP-Configuration.md +++ b/SMTP-Configuration.md @@ -1,5 +1,5 @@ > [!NOTE] -> If you don't set up SMTP, Vaultwarden might be unable to send verification emails when you log in outside web vault, browser extension and mobile apps (e.g. Bitwarden CLI), and might secretly reject the authentication request. To bypass this behaviour, set up two-factor authentication on your account. See https://github.com/dani-garcia/vaultwarden/discussions/6410 +> If you choose not to set up SMTP, Vaultwarden might be unable to send verification emails when you log in outside web vault, browser extension and mobile apps (e.g. Bitwarden CLI), and might secretly reject the authentication request. To bypass this behaviour, set up two-factor authentication on your account. See https://github.com/dani-garcia/vaultwarden/discussions/6410 You can configure vaultwarden to send emails via a SMTP agent: