Skip to content
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

Open
alvaro893 opened this issue Jan 17, 2020 · 9 comments
Open

Email encryption #76

alvaro893 opened this issue Jan 17, 2020 · 9 comments

Comments

@alvaro893
Copy link

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?
email-verification

@skywa04885
Copy link

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

@alvaro893
Copy link
Author

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
Copy link

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

@zavr-1
Copy link

zavr-1 commented Jan 22, 2020

@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
Copy link

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
Copy link

@zavr-1 This issue is the same as the one I did: #75 and I assure you that TLS is not implemented.

@markgrin markgrin mentioned this issue Aug 30, 2020
9 tasks
@markgrin
Copy link

markgrin commented Aug 30, 2020

@micktaiwan @zavr-1 @skywa04885 @alvaro893
Could you test this pull? It might be the solution #80 . It worked for me

Thank you

@markgrin
Copy link

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
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants