Setting the sending engine globally is prone to error about nodemailer HOT 6 CLOSED

This is known issue and is related to the fact that Nodemailer was initially meant to be used as a SMTP client. Sendmail and Amazon SES support were added later ad hoc. There is a way to use local SMTP settings which override global ones but no way to do this with sendmail or SES.

{
    from: "[email protected]",
    to: "[email protected]",
    subject: "subject line",
    text: "message body",
    server:{
        host:"localhost",
        // server settings to follow
    }
}

from nodemailer.

So what is the future for this issue? Will it be fixed in the next version?

Would like us to work on improving this in our fork for you take a look at?

On 23 September 2011 11:08, Andris Reinman
[email protected]
wrote:

This is known issue and is related to the fact that Nodemailer was initially meant to be used as a SMTP client. Sendmail and Amazon SES support were added later ad hoc. There is a way to use local SMTP settings which override global ones but no way to do this with sendmail or SES.

   {
       from: "[email protected]",
       to: "[email protected]",
       subject: "subject line",
       text: "message body",
       server:{
           host:"localhost",
           // server settings to follow
       }
   }

Reply to this email directly or view it on GitHub:
https://github.com/andris9/Nodemailer/issues/45#issuecomment-2177144

[email protected]
Chief Technology Officer

Direct: +44 2030 516115
Mobile: +44 7881 550999
Conference: +44 20 3051 6144

Clock Limited
The Old School House
Bridge Road, Hunton Bridge,
Kings Langley, WD4 8RQ
Switchboard: +44 1923 261166

www.clock.co.uk

http://twitter.com/clock
http://blog.clock.co.uk/
http://delicious.com/clocklimited

www.clock.co.uk/email-disclaimer

clock.® is a Registered Trademark of Clock Limited in the European
Community and other territories

from nodemailer.

I don't have any good ideas regarding this problem, so you're welcome to fix it and send me a pull request. The only condition being that it shouldn't break existing code.

from nodemailer.

Okay we'll take a look and send you a pull request.

It will break existing code in the rare edge case where people are
exploiting the global nodemailer.sendmail to change the transport
globally. Even though that is a weird use-case, you could wait until
you go to 0.3.0 to fix the problem.

Paul

On 26 September 2011 11:32, Andris Reinman
[email protected]
wrote:

I don't have any good ideas regarding this problem, so you're welcome to fix it and send me a pull request. The only condition being that it shouldn't break existing code.

Reply to this email directly or view it on GitHub:
https://github.com/andris9/Nodemailer/issues/45#issuecomment-2196803

[email protected]
Chief Technology Officer

Direct: +44 2030 516115
Mobile: +44 7881 550999
Conference: +44 20 3051 6144

Clock Limited
The Old School House
Bridge Road, Hunton Bridge,
Kings Langley, WD4 8RQ
Switchboard: +44 1923 261166

www.clock.co.uk

http://twitter.com/clock
http://blog.clock.co.uk/
http://delicious.com/clocklimited

www.clock.co.uk/email-disclaimer

clock.® is a Registered Trademark of Clock Limited in the European
Community and other territories

from nodemailer.

The new v0.3 branch doesn't use global settings anymore but dedicated "transport" objects

from nodemailer.

Nice.

from nodemailer.