-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Switch to modern nodemailer 4, Node 4 version. Fix #8591 #8605
Conversation
edemaine
commented
Apr 16, 2017
- Most critically, use a pool instead of direct SMTP connection, to handle dropped connections and increase throughput, like mail module 1.1. (Meteor email keeps SMTP connection opened and causes error with some email providers #8591)
- New nodemailer's sendMail wants an options object, not a MailComposer object. Luckily, a MailComposer object has a "mail" field that remembers the original options, so we can keep original behavior.
- However, we no longer support the mailComposer option set to a compiled MailComposer object (functionality that was briefly added in 1.2.0).
- nodemailer does SMTP URL parsing now automatically for us, simplifying code.
- Tests' outputs now end with additional "\r\n"
- Drop underscore package dependency (no longer needed)
* Most critically, use a pool instead of direct SMTP connection, to handle dropped connections and increase throughput, like mail module 1.1. (meteor#8591) * New nodemailer's sendMail wants an options object, not a MailComposer object. Luckily, a MailComposer object has a "mail" field that remembers the original options, so we can keep original behavior. * However, we no longer support the mailComposer option set to a compiled MailComposer object (functionality that was briefly added in 1.2.0). * nodemailer does SMTP URL parsing now automatically for us, simplifying code. * Tests' outputs now end with additional "\r\n" * Drop underscore package dependency (no longer needed)
Just an FYI! This is a relatively easy situation to have happen with Git submodules (which we use), but this PR had the To rectify this (I'd like to look at this early this coming week!), I've merged the most recent In the future, in addition to the usual syncing a fork, it should just be a matter of running:
...if you ever notice the following in
😄 |
We are waiting on this to close: |
@abernix Thanks!! I was confused about that; your explanation makes sense. Thanks for both fixing it and explaining so I don't make the mistake in the future. |
* snake_cased => camelCased for some local variables. * Added curly-brackets to `if`s. * Removed trailing spaces. * Removed commented-out code. * Removed older doc text and changed some links.
* Switch to modern nodemailer 4, Node 4 version. Fix #8591 * Most critically, use a pool instead of direct SMTP connection, to handle dropped connections and increase throughput, like mail module 1.1. (#8591) * New nodemailer's sendMail wants an options object, not a MailComposer object. Luckily, a MailComposer object has a "mail" field that remembers the original options, so we can keep original behavior. * However, we no longer support the mailComposer option set to a compiled MailComposer object (functionality that was briefly added in 1.2.0). * nodemailer does SMTP URL parsing now automatically for us, simplifying code. * Tests' outputs now end with additional "\r\n" * Drop underscore package dependency (no longer needed) * General formatting/style cleanup for `packages/email`. * snake_cased => camelCased for some local variables. * Added curly-brackets to `if`s. * Removed trailing spaces. * Removed commented-out code. * Removed older doc text and changed some links. * Get rid of back-and-forth assigning of `mailUrlString`.
Yes, most of these were just general clean-up, certainly not specific to any of your additions/changes, but made sense to do while testing/reviewing it already. 😉 |
* Switch to modern nodemailer 4, Node 4 version. Fix #8591 * Most critically, use a pool instead of direct SMTP connection, to handle dropped connections and increase throughput, like mail module 1.1. (#8591) * New nodemailer's sendMail wants an options object, not a MailComposer object. Luckily, a MailComposer object has a "mail" field that remembers the original options, so we can keep original behavior. * However, we no longer support the mailComposer option set to a compiled MailComposer object (functionality that was briefly added in 1.2.0). * nodemailer does SMTP URL parsing now automatically for us, simplifying code. * Tests' outputs now end with additional "\r\n" * Drop underscore package dependency (no longer needed) * General formatting/style cleanup for `packages/email`. * snake_cased => camelCased for some local variables. * Added curly-brackets to `if`s. * Removed trailing spaces. * Removed commented-out code. * Removed older doc text and changed some links. * Get rid of back-and-forth assigning of `mailUrlString`.
* Switch to modern nodemailer 4, Node 4 version. Fix #8591 * Most critically, use a pool instead of direct SMTP connection, to handle dropped connections and increase throughput, like mail module 1.1. (#8591) * New nodemailer's sendMail wants an options object, not a MailComposer object. Luckily, a MailComposer object has a "mail" field that remembers the original options, so we can keep original behavior. * However, we no longer support the mailComposer option set to a compiled MailComposer object (functionality that was briefly added in 1.2.0). * nodemailer does SMTP URL parsing now automatically for us, simplifying code. * Tests' outputs now end with additional "\r\n" * Drop underscore package dependency (no longer needed) * General formatting/style cleanup for `packages/email`. * snake_cased => camelCased for some local variables. * Added curly-brackets to `if`s. * Removed trailing spaces. * Removed commented-out code. * Removed older doc text and changed some links. * Get rid of back-and-forth assigning of `mailUrlString`.