2.0.0 ready to go?
See original GitHub issueI think its time. Everything in the milestone is complete, and the docs site is up and running. (except for the during
inconsistency issue, which I think is just a docs fix)
I think 2.0.0 is ready for to be released into the wild!
cc @megawac
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:22 (1 by maintainers)
Top Results From Across the Web
SMTP: STARTTLS failed (code: 220, response: 2.0.0 Ready to ...
Suddenly my web start to give this error when trying to send an email: [SMTP: STARTTLS failed (code: 220, response: 2.0.0 Ready to...
Read more >authentication failure STARTTLS failed code 220 response
Unable to log in. Check SMTP settings. authentication failure [SMTP: STARTTLS failed (code: 220, response: 2.0.0 SMTP server ready)]. I think ...
Read more >authentication failure [SMTP: STARTTLS failed (code: 220 ...
The undocumented parameter: socket_options , let me authenticate when I got this error: authentication failure [SMTP: STARTTLS failed (code: ...
Read more >Office 365 SMTP servers started getting random ...
The errors are random, and if resending after the error normally they go right through. It seems both of them quit communicating with...
Read more >How to use SMTP to send mail to some host? - Server Fault
So far I've tried: 220 mx.google.com ESMTP y14sm3079810ibf.45 HELO 250 mx.google.com at your service STARTTLS 220 2.0.0 Ready to start ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
2.0.0 is live! https://www.npmjs.com/package/async
Now we wait for the inevitable bug reports… 😵 😅