-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
SSL3 Errror with outlook.com #165
Comments
Hi, which version of Nodemailer and node are you using? This could be duplicate of https://github.com/andris9/Nodemailer/issues/155 |
node: v0.10.11 |
To get Hotmail running you should either not define the host and port by yourself but use a {
service: "hotmail",
auth: {
user: '********@outlook.com',
pass: '********'
}
} Or alternatively add an addtional {
host: 'smtp.live.com', // hostname
secureConnection: false, // use SSL
port: 587, // port for secure SMTP
auth: {
user: '********@outlook.com',
pass: '********'
},
tls:{
ciphers:'SSLv3'
}
} |
I am having the same issue. I am connecting to a private email server. Here is my configuration: var smtpTransport = nodemailer.createTransport("SMTP", {
host: "***.***.***.***",
secureConnection: true,
port: 465,
auth: {
user: "****",
pass: "****"
},
tls: {
ciphers:'SSLv3'
}
}); I receive the same error as the OP:
I can successfully connect to the server via openssl:
When I connect this way, the server responds with:
|
@andris9 What does the tls: { ciphers:'SSLv3' } do? I am trying to understand the reason behind adding the tls option |
setting the port from 587 to 465 solved my problem.
After changed the port to 465: |
Please help me with this error |
Guys I have the same error 2019-04-20 10:52 +04:30: { [Error: 140529796826944:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:252: |
ran into this issue, discovered i was using an old version of nodemailer. updating to the latest version and removing a bunch of other outdated code fixed it for me |
add
|
live.com a bit different from office365 enterprise and we get same error. 587 is not available on MX record for direct send. It used TLS on 25. The smtp relay host with auth (user licence needed) would be smtp.office365.com. We don't use this option. The other option is direct send to MX server (another DNS record) and a connector to allow relay based on IP of the sender. This is what we chose. It used to work. It uses port 25 only. |
Hi I was setting up nodemailer to work with outlook.com and got the following error.
This is the config i was using.
The text was updated successfully, but these errors were encountered: