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 1.2.1 Error: Greeting never received - Nodemailer #8612

Closed
ixdi opened this Issue Apr 19, 2017 · 17 comments

Comments

Projects
None yet
7 participants
@ixdi

ixdi commented Apr 19, 2017

Hi,

The new version of email package 1.2.1 gives us an

Exception while invoking method 'forgotPassword' { stack: 'Error: Greeting never received\n at Mail._syncSendMail }

Maybe it's related with this issue in Nodemailer and the secure option.

nodemailer/nodemailer#441

Thanks

@lucfranken

This comment has been minimized.

Show comment
Hide comment
@lucfranken

lucfranken Apr 20, 2017

Contributor

Can confirm that this happens also with 1.2.0 updated from 1.1.18 with the standard Meteor update. We are using Mailgun as e-mail provider.

Contributor

lucfranken commented Apr 20, 2017

Can confirm that this happens also with 1.2.0 updated from 1.1.18 with the standard Meteor update. We are using Mailgun as e-mail provider.

@deeeed

This comment has been minimized.

Show comment
Hide comment
@deeeed

deeeed Apr 20, 2017

Same issue for me, any known workaround ?

deeeed commented Apr 20, 2017

Same issue for me, any known workaround ?

@abernix

This comment has been minimized.

Show comment
Hide comment
@abernix

abernix Apr 20, 2017

Member

This sounds related to the discussion that started in this thread.

Are any of you using a secure SMTP port number (465, 587, etc.) but using the insecure smtp: schema (rather than smtps:) in your MAIL_URL?

Member

abernix commented Apr 20, 2017

This sounds related to the discussion that started in this thread.

Are any of you using a secure SMTP port number (465, 587, etc.) but using the insecure smtp: schema (rather than smtps:) in your MAIL_URL?

@deeeed

This comment has been minimized.

Show comment
Hide comment
@deeeed

deeeed Apr 20, 2017

yes :) thanks

deeeed commented Apr 20, 2017

yes :) thanks

@ixdi

This comment has been minimized.

Show comment
Hide comment
@ixdi

ixdi Apr 21, 2017

Thank you! Sorry about I didn't saw the related issue.

ixdi commented Apr 21, 2017

Thank you! Sorry about I didn't saw the related issue.

@hwillson

This comment has been minimized.

Show comment
Hide comment
@hwillson

hwillson Apr 21, 2017

Member

@deeeed @ixdi I can't quite tell from your last comments; did lining up your secure SMTP port number choice with smtps: fix this for you? Let us know if this can be closed. Thanks!

Member

hwillson commented Apr 21, 2017

@deeeed @ixdi I can't quite tell from your last comments; did lining up your secure SMTP port number choice with smtps: fix this for you? Let us know if this can be closed. Thanks!

@deeeed

This comment has been minimized.

Show comment
Hide comment
@deeeed

deeeed Apr 22, 2017

@hwillson yes it is fixed BUT I had to upgrade node to 4.5.0.
Apparently "smtps" causes an error with nodemailer for version below 4.5.0:

2|YueLaoAp | TypeError: this is not a typed array.
2|YueLaoAp |     at Function.from (native)
2|YueLaoAp |     at LastNewline._flush (/opt/pm2-meteor/YueLaoApp/bundle/programs/server/npm/node_modules/meteor/email/node_modules/node4mailer/lib/mime-node/last-newline.js:28:26)
2|YueLaoAp |     at LastNewline.<anonymous> (_stream_transform.js:118:12)
2|YueLaoAp |     at LastNewline.g (events.js:260:16)
2|YueLaoAp |     at emitNone (events.js:67:13)
2|YueLaoAp |     at LastNewline.emit (events.js:166:7)
2|YueLaoAp |     at prefinish (_stream_writable.js:471:12)
2|YueLaoAp |     at finishMaybe (_stream_writable.js:479:7)
2|YueLaoAp |     at endWritable (_stream_writable.js:491:3)
2|YueLaoAp |     at LastNewline.Writable.end (_stream_writable.js:456:5)
2|YueLaoAp | 2017-04-22 07:20:45 ERROR uncaughtException: this is not a typed array.

http://stackoverflow.com/questions/42331751/typeerror-this-is-not-a-typed-array-with-ws-js-in-node-js

deeeed commented Apr 22, 2017

@hwillson yes it is fixed BUT I had to upgrade node to 4.5.0.
Apparently "smtps" causes an error with nodemailer for version below 4.5.0:

2|YueLaoAp | TypeError: this is not a typed array.
2|YueLaoAp |     at Function.from (native)
2|YueLaoAp |     at LastNewline._flush (/opt/pm2-meteor/YueLaoApp/bundle/programs/server/npm/node_modules/meteor/email/node_modules/node4mailer/lib/mime-node/last-newline.js:28:26)
2|YueLaoAp |     at LastNewline.<anonymous> (_stream_transform.js:118:12)
2|YueLaoAp |     at LastNewline.g (events.js:260:16)
2|YueLaoAp |     at emitNone (events.js:67:13)
2|YueLaoAp |     at LastNewline.emit (events.js:166:7)
2|YueLaoAp |     at prefinish (_stream_writable.js:471:12)
2|YueLaoAp |     at finishMaybe (_stream_writable.js:479:7)
2|YueLaoAp |     at endWritable (_stream_writable.js:491:3)
2|YueLaoAp |     at LastNewline.Writable.end (_stream_writable.js:456:5)
2|YueLaoAp | 2017-04-22 07:20:45 ERROR uncaughtException: this is not a typed array.

http://stackoverflow.com/questions/42331751/typeerror-this-is-not-a-typed-array-with-ws-js-in-node-js

@edemaine

This comment has been minimized.

Show comment
Hide comment
@edemaine

edemaine Apr 22, 2017

Contributor

@deeeed I'm confused: doesn't Meteor depend on Node 4.8.1?

@abernix Should I/we restore the old behavior of "port 465 implies smtps"? (My personal opinion is that the new behavior is "more correct", but it is also less compatible.) Otherwise we should put a warning in the release notes. (Incidentally, I didn't know that port 465 has been deprecated since 1999, though is still in active use. But I don't see anything about assuming smtp vs. smtps.)

Contributor

edemaine commented Apr 22, 2017

@deeeed I'm confused: doesn't Meteor depend on Node 4.8.1?

@abernix Should I/we restore the old behavior of "port 465 implies smtps"? (My personal opinion is that the new behavior is "more correct", but it is also less compatible.) Otherwise we should put a warning in the release notes. (Incidentally, I didn't know that port 465 has been deprecated since 1999, though is still in active use. But I don't see anything about assuming smtp vs. smtps.)

@deeeed

This comment has been minimized.

Show comment
Hide comment
@deeeed

deeeed Apr 22, 2017

@edemaine right! So the problem was from me using pm2 to run my app and not checking version constraints...

deeeed commented Apr 22, 2017

@edemaine right! So the problem was from me using pm2 to run my app and not checking version constraints...

@ixdi

This comment has been minimized.

Show comment
Hide comment
@ixdi

ixdi Apr 22, 2017

@hwillson Sorry but when we deployed to Galaxy with smtps and email@1.2.1 the error persisted.

Error: Greeting never received

So the error is not resolved. There's no advise for us when we deploy with email@1.2.0

ixdi commented Apr 22, 2017

@hwillson Sorry but when we deployed to Galaxy with smtps and email@1.2.1 the error persisted.

Error: Greeting never received

So the error is not resolved. There's no advise for us when we deploy with email@1.2.0

@edemaine

This comment has been minimized.

Show comment
Hide comment
@edemaine

edemaine Apr 22, 2017

Contributor

@ixdi What does your MAIL_URL look like?

Contributor

edemaine commented Apr 22, 2017

@ixdi What does your MAIL_URL look like?

@ixdi

This comment has been minimized.

Show comment
Hide comment
@ixdi

ixdi Apr 22, 2017

@edemaine

"MAIL_URL":"smtps://<user>:<password>@smtp.mailgun.org:465"

ixdi commented Apr 22, 2017

@edemaine

"MAIL_URL":"smtps://<user>:<password>@smtp.mailgun.org:465"
@edemaine

This comment has been minimized.

Show comment
Hide comment
@edemaine

edemaine Apr 22, 2017

Contributor

@ixdi Did you restart/redeploy Meteor after resetting that variable? Sorry for asking the obvious, but I'm pretty sure it's the smtp vs. smtps issue not yet resolved. (Regarding your original question, there's no longer a "secure" option in Nodemailer -- it's extracted directly from the URL.)

Contributor

edemaine commented Apr 22, 2017

@ixdi Did you restart/redeploy Meteor after resetting that variable? Sorry for asking the obvious, but I'm pretty sure it's the smtp vs. smtps issue not yet resolved. (Regarding your original question, there's no longer a "secure" option in Nodemailer -- it's extracted directly from the URL.)

@ixdi

This comment has been minimized.

Show comment
Hide comment
@ixdi

ixdi Apr 22, 2017

@edemaine You are right! It's obvious but we deployed without settings.json.
We have deployed an update now and there's no advise, it's resolved!

Thank you!!

ixdi commented Apr 22, 2017

@edemaine You are right! It's obvious but we deployed without settings.json.
We have deployed an update now and there's no advise, it's resolved!

Thank you!!

@edemaine

This comment has been minimized.

Show comment
Hide comment
@edemaine

edemaine Apr 22, 2017

Contributor

Awesome!! Sounds like 1.2.1 is working for everyone then.

Contributor

edemaine commented Apr 22, 2017

Awesome!! Sounds like 1.2.1 is working for everyone then.

@hwillson

This comment has been minimized.

Show comment
Hide comment
@hwillson

hwillson Apr 23, 2017

Member

Excellent news! Closing - thanks everyone!

Member

hwillson commented Apr 23, 2017

Excellent news! Closing - thanks everyone!

@hwillson hwillson closed this Apr 23, 2017

@mgscreativa

This comment has been minimized.

Show comment
Hide comment
@mgscreativa

mgscreativa May 15, 2017

Hi! I just filled another bug here #8696 I think it's not related with this one so maybe would be wise to check it out...

mgscreativa commented May 15, 2017

Hi! I just filled another bug here #8696 I think it's not related with this one so maybe would be wise to check it out...

noahsw added a commit to winsleague/winsleague that referenced this issue Nov 22, 2017

noahsw added a commit to winsleague/winsleague that referenced this issue Nov 22, 2017

Feature/416 email smtps (#420)
* per meteor/meteor#8612 moved to using smtps://

* Clearer logging
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment