[PR #3572] [MERGED] 2FA Confirmation Code Email subject line change to fix triggering Google spam blocker #3277

Closed
opened 2026-02-05 05:21:16 +03:00 by OVERLORD · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/dani-garcia/vaultwarden/pull/3572
Author: @aureateflux
Created: 6/11/2023
Status: Merged
Merged: 10/21/2023
Merged by: @dani-garcia

Base: mainHead: 2FA-Email-Subject-Line-fix


📝 Commits (5)

  • bb87b64 Update twofactor_email.hbs subject line to avoid triggering gmail content filter
  • 2228dd3 Update twofactor_email.html.hbs subject line to avoid triggering gmail content filter
  • c3081b5 Update twofactor_email.hbs
  • c4fc111 Update twofactor_email.hbs
  • 9b9fc74 Update twofactor_email.html.hbs

📊 Changes

2 files changed (+4 additions, -4 deletions)

View changed files

📝 src/static/templates/email/twofactor_email.hbs (+2 -2)
📝 src/static/templates/email/twofactor_email.html.hbs (+2 -2)

📄 Description

Changed subject lines in both the regular and HTML version of the 2FA confirmation email because previous subject line ("Your Two-step Login Verification Code") was being blocked by Google's servers.

The new subject line is "Vaultwarden Confirmation Code"

Please comment if a different subject line is preferable for any reason.

I've only tested this subject line with the emailer configured to use a Google SMTP server. If you have Vaultwarden configured to use another email service, please test this template using your email service.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/dani-garcia/vaultwarden/pull/3572 **Author:** [@aureateflux](https://github.com/aureateflux) **Created:** 6/11/2023 **Status:** ✅ Merged **Merged:** 10/21/2023 **Merged by:** [@dani-garcia](https://github.com/dani-garcia) **Base:** `main` ← **Head:** `2FA-Email-Subject-Line-fix` --- ### 📝 Commits (5) - [`bb87b64`](https://github.com/dani-garcia/vaultwarden/commit/bb87b64bb6cde8d9b27b424b0e5f48b022c0f1bb) Update twofactor_email.hbs subject line to avoid triggering gmail content filter - [`2228dd3`](https://github.com/dani-garcia/vaultwarden/commit/2228dd3015829805ec37bc1066355655433f0ef8) Update twofactor_email.html.hbs subject line to avoid triggering gmail content filter - [`c3081b5`](https://github.com/dani-garcia/vaultwarden/commit/c3081b58ee729249b23cf5e90026597b21cf3a03) Update twofactor_email.hbs - [`c4fc111`](https://github.com/dani-garcia/vaultwarden/commit/c4fc1117132f3544e4aac46d00a2c1c5116e110d) Update twofactor_email.hbs - [`9b9fc74`](https://github.com/dani-garcia/vaultwarden/commit/9b9fc74636b21ac7bcfc2628bcbb81df0c158a36) Update twofactor_email.html.hbs ### 📊 Changes **2 files changed** (+4 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `src/static/templates/email/twofactor_email.hbs` (+2 -2) 📝 `src/static/templates/email/twofactor_email.html.hbs` (+2 -2) </details> ### 📄 Description Changed subject lines in both the regular and HTML version of the 2FA confirmation email because previous subject line ("Your Two-step Login Verification Code") was being blocked by Google's servers. The new subject line is "Vaultwarden Confirmation Code" Please comment if a different subject line is preferable for any reason. I've only tested this subject line with the emailer configured to use a Google SMTP server. If you have Vaultwarden configured to use another email service, please test this template using your email service. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-05 05:21:16 +03:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#3277