starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-26 01:35:54 +03:00
Code Issues 39 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #1855] verification mail in Spam #1081

New issue
Closed
opened 2026-03-03 02:06:06 +03:00 by kerem · 8 comments
kerem commented 2026-03-03 02:06:06 +03:00
Owner
Copy link

Originally created by @Skyfay on GitHub (Jul 16, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1855

I noticed that the verification emails always end up in spam.
The parameters should possibly be adjusted so that they are not declared as spam.

Originally created by @Skyfay on GitHub (Jul 16, 2021). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1855 I noticed that the verification emails always end up in spam. The parameters should possibly be adjusted so that they are not declared as spam.
kerem closed this issue 2026-03-03 02:06:07 +03:00
kerem commented 2026-03-03 02:06:07 +03:00
Author
Owner
Copy link

@BlackDex commented on GitHub (Jul 16, 2021):

There are multiple reasons why an email could be marked as spam. So this report isn't going to help us. We need to know why it was triggered.
Also, spf, dkim and dmarc configurations can play an issue here which is out of the control of Vaultwarden

<!-- gh-comment-id:881722373 --> @BlackDex commented on GitHub (Jul 16, 2021): There are multiple reasons why an email could be marked as spam. So this report isn't going to help us. We need to know why it was triggered. Also, spf, dkim and dmarc configurations can play an issue here which is out of the control of Vaultwarden
kerem commented 2026-03-03 02:06:07 +03:00
Author
Owner
Copy link

@Masgalor commented on GitHub (Jul 19, 2021):

If you want to better understand why your mails get marked as spam I would recommend to use Mail-Tester or a similar service. They will give you a detailed report about why your mails arent trustworthy enough.

<!-- gh-comment-id:882473081 --> @Masgalor commented on GitHub (Jul 19, 2021): If you want to better understand why your mails get marked as spam I would recommend to use [Mail-Tester](https://www.mail-tester.com/) or a similar service. They will give you a detailed report about why your mails arent trustworthy enough.
kerem commented 2026-03-03 02:06:08 +03:00
Author
Owner
Copy link

@Skyfay commented on GitHub (Jul 19, 2021):

image
image
image
The rest is good everywhere

<!-- gh-comment-id:882501361 --> @Skyfay commented on GitHub (Jul 19, 2021): ![image](https://user-images.githubusercontent.com/76796007/126158422-3dc0ffa4-6441-46fe-9c3f-a6441f105ed5.png) ![image](https://user-images.githubusercontent.com/76796007/126158472-07b2e9b9-cf31-4491-b54a-e20aa3c004ea.png) ![image](https://user-images.githubusercontent.com/76796007/126158488-7bdf4429-7e1d-4858-850c-ba717b0340c1.png) The rest is good everywhere
kerem commented 2026-03-03 02:06:08 +03:00
Author
Owner
Copy link

@BlackDex commented on GitHub (Jul 19, 2021):

@Masgalor I used that already, and i have think i have fixed all issues.
But since i do not know what type of spam filtering the reporter is using and that mail-tester only uses the default spamassissin rules, it's hard to tell what triggered it.

<!-- gh-comment-id:882501382 --> @BlackDex commented on GitHub (Jul 19, 2021): @Masgalor I used that already, and i have think i have fixed all issues. But since i do not know what type of spam filtering the reporter is using and that mail-tester only uses the default spamassissin rules, it's hard to tell what triggered it.
kerem commented 2026-03-03 02:06:08 +03:00
Author
Owner
Copy link

@BlackDex commented on GitHub (Jul 19, 2021):

@Skyfay, it looks to me it's marked as spam because of the items i mentioned which are out of control of vaultwarden.
SPF, DKIM and DMARC.

<!-- gh-comment-id:882502208 --> @BlackDex commented on GitHub (Jul 19, 2021): @Skyfay, it looks to me it's marked as spam because of the items i mentioned which are out of control of vaultwarden. SPF, DKIM and DMARC.
kerem commented 2026-03-03 02:06:08 +03:00
Author
Owner
Copy link

@Skyfay commented on GitHub (Jul 19, 2021):

@BlackDex So is the problem with Bitwarden or my provider?

<!-- gh-comment-id:882502831 --> @Skyfay commented on GitHub (Jul 19, 2021): @BlackDex So is the problem with Bitwarden or my provider?
kerem commented 2026-03-03 02:06:08 +03:00
Author
Owner
Copy link

@Masgalor commented on GitHub (Jul 19, 2021):

@BlackDex my comment was mostly meant for Skyfy because I agree with you that the problem is most likely not related to vaultwarden.

@Skyfay the quote "SpamAssassin mag deine E-Mail" (SpamAssassin likes your E-Mail) indicates that the content of the mail is not suspicious. But those entries with a negativ number in the score are missing PTR-Record, invalid SPF-Record and missing DKIM-signature. All three of them are problems with mailserver not vaultwarden.

I assume most mail server would classify this mail as spam, for example my mine would definitly mark it as spam.

<!-- gh-comment-id:882515355 --> @Masgalor commented on GitHub (Jul 19, 2021): @BlackDex my comment was mostly meant for Skyfy because I agree with you that the problem is most likely not related to vaultwarden. @Skyfay the quote "SpamAssassin mag deine E-Mail" (SpamAssassin likes your E-Mail) indicates that the content of the mail is not suspicious. But those entries with a negativ number in the score are missing PTR-Record, invalid SPF-Record and missing DKIM-signature. All three of them are problems with mailserver not vaultwarden. I assume most mail server would classify this mail as spam, for example my mine would definitly mark it as spam.
kerem commented 2026-03-03 02:06:08 +03:00
Author
Owner
Copy link

@Skyfay commented on GitHub (Jul 19, 2021):

@Masgalor I added the SPF record and now it no longer ends up in spam!
thanks

<!-- gh-comment-id:882532961 --> @Skyfay commented on GitHub (Jul 19, 2021): @Masgalor I added the SPF record and now it no longer ends up in spam! thanks
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
revert-7033-patch-1
cached-config-operations
test_dylint
1.35.8
1.35.7
1.35.6
1.35.5
1.35.4
1.35.3
1.35.2
1.35.1
1.35.0
1.34.3
1.34.2
1.34.1
1.34.0
1.33.2
1.33.1
1.33.0
1.32.7
1.32.6
1.32.5
1.32.4
1.32.3
1.32.2
1.32.1
1.32.0
1.31.0
1.30.5
1.30.4
1.30.3
1.30.2
1.30.1
1.30.0
1.29.2
1.29.1
1.29.0
1.28.1
1.28.0
1.27.0
1.26.0
1.25.2
1.25.1
1.25.0
1.24.0
1.23.1
1.23.0
1.22.2
1.22.1
1.22.0
1.21.0
1.20.0
1.19.0
1.18.0
1.17.0
1.16.3
1.16.2
1.16.1
1.16.0
1.15.1
1.15.0
1.14.2
1.14.1
1.14
1.13.1
1.13.0
1.12.0
1.11.0
1.10.0
1.9.1
1.9.0
1.8.0
1.7.0
1.6.1
1.6.0
1.5.0
1.4.0
1.3.0
1.2.0
1.1.0
1.0.0
0.13.0
0.12.0
0.11.0
0.10.0
0.9.0
Labels
Clear 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

Mirrored from GitHub Pull Request

  
question

   
troubleshooting

   
wontfix
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#1081
No description provided.