deep-mail

deepjs wrapper for nodemailer and postmark.

For transporter config parameters see nodemailer docs.

    require("deep-mail")
    // configure default transporter
    .defaultTransporter(deep.mail.nodemailer("SMTP",{	
        service: "Gmail",
        auth: {
            user: "[e-mail]",
            pass: "userpass"
        }
    }));
 
    //....
 
    deep.mail({	// use default transporter to send email
        from: "Fred Foo ✔ <[e-mail]>", // sender address
        to: "[e-mail], [e-mail]", // list of receivers
        subject: "Hello ✔", // Subject line
        text: "Hello world ✔", // plaintext body       
        html: "<b>Hello world ✔</b>" // html body
    })
    .log();
 
    //...
 
    deep(myText)
    .mail({	// use default transporter to send chain's value(s) (as JSON) through email
        from: "Fred Foo ✔ <[e-mail]>", // sender address
        to: "[e-mail], [e-mail]", // list of receivers
        subject: "Hello ✔", // Subject line
        //text: "Hello world ✔ : { value }", // plaintext body       ==> if you provides text here : it will be interpreted with chain's value(s) and used as email body
        //html: "<b>Hello world ✔ : { value }</b>" // html body      ==> if you provide a template here (i.e. "swig::you-template.html") : it will be used with chain(s value(s) as context. else : it will be interpreted with chain's value(s)
    })
    .log();

You could use deep.context to manage contextualised transporter.

 
    deep.when(...)
    .context("deep-mail-transporter", deep.mail.postmark("YOURAPIKEY"))
    .done(function(){
        //...
        deep.mail({ ... }).log();
    });

deep.mail will first look after a 'deep-mail-transporter' property in deep.context before trying to use the default (general) one.

see deepjs docs on concurrent context management to fully grasp the utility of such manipulation

full API :

 
deep.mail(params, datas, transporter, closeAfter)...;
 
// and
 
deep(...).mail(params, transporter, closeAfter)...;