Email encryption - Githubissues

guileen / node-sendmail

send mail without setting up a SMTP server

http://guileen.github.com/node-sendmail

MIT License

559 stars 110 forks source link

Email encryption #76

Open alvaro893 opened 4 years ago

alvaro893 commented 4 years ago

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?

skywa04885 commented 4 years ago

I made a library myself, it supports start tls, you can try it: fannst-nodemailer

alvaro893 commented 4 years ago

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?

skywa04885 commented 4 years ago

You need to combine it with SPF record, then it will most likely not end in spam

zavr-1 commented 4 years ago

@skywa04885 some content in your package is not appropriate (the interval function). otherwise good job but it lacks documentation. @alvaro893 the client in this package performs a TLS upgrade so it's strange you see this... if you want it not to be spam 100%, use a relay like https://app.smtp2go.com they have domain verification also unlike sendgrid which doesn't do it on free plan.

micktaiwan commented 4 years ago

This service is great to check if your email content will be considered as spam or not https://www.mail-tester.com/

It is not perfect as some servers (as Yahoo) does not rely only on email content but also on Yahoo users' past complaints

micktaiwan commented 4 years ago

@zavr-1 This issue is the same as the one I did: https://github.com/guileen/node-sendmail/issues/75 and I assure you that TLS is not implemented.

markgrin commented 4 years ago

@micktaiwan @zavr-1 @skywa04885 @alvaro893 Could you test this pull? It might be the solution https://github.com/guileen/node-sendmail/pull/80 . It worked for me

Thank you

markgrin commented 4 years ago

From RFC 3207

A publicly-referenced SMTP server would probably want to accept any verifiable certificate from an SMTP client, and would possibly want to put distinguishing information about the certificate in the Received header of messages that were relayed or submitted from the client.

svaraborut commented 3 years ago

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?