-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Email encryption #76
Comments
I made a library myself, it supports start tls, you can try it: fannst-nodemailer |
Thanks I'll check it out. Do you now if having emails encrypted with you library would be enough for them not to be labeled as spam? |
You need to combine it with SPF record, then it will most likely not end in spam |
@skywa04885 some content in your package is not appropriate (the interval function). otherwise good job but it lacks documentation. |
This service is great to check if your email content will be considered as spam or not It is not perfect as some servers (as Yahoo) does not rely only on email content but also on Yahoo users' past complaints |
@micktaiwan @zavr-1 @skywa04885 @alvaro893 Thank you |
From RFC 3207
|
Hello, I see the repo has TLS upgrade present, but the NPM repo does not. Is the current master version stable? why it is not in sync with NPM? |
Currently I am using sendmail to verify users in my app (hosted in azure), it works but some don't receive at all, I guess their emails are considering this as spam.
I have noticed that when receiving these emails in my gmail account reports they are not encrypted. Is there a way to make them encrypted?
The text was updated successfully, but these errors were encountered: