npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@umpacken/node-mailin

v2.7.0

Published

Artisanal inbound emails for every web app using nodejs

Downloads

20

Readme

IMPORTANT: This is the repack of the original version with updated dependencies

Node-Mailin

Artisanal inbound emails for every web app

Node-Mailin is an smtp server that listens for emails, parses as json. It checks the incoming emails dkim, spf, spam score (using spamassassin) and tells you in which language the email is written.

Node-Mailin can be used as a standalone application directly from the command line, or embedded inside a node application.

Initial setup

Dependencies

Node-Mailin can run without any dependencies other than node itself, but having them allow you to use some additional features.

So first make sure the node is available, and the node command as well. On Debian/Ubuntu boxes:

sudo aptitude install nodejs ; sudo ln -s $(which nodejs) /usr/bin/node

To handle the spam score computation, Node-Mailin depends on spamassassin and its server interface spamc. Both should be available as packages on your machine. For instance on Debian/Ubuntu boxes:

Spamassassin is not enabled by default, enable it in with update-rc.d spamassassin enable command.

sudo aptitude install spamassassin spamc
sudo update-rc.d spamassassin enable
sudo service spamassassin start

Node versions

Current LTS and LTS+ versions.

The crux: setting up your DNS correctly

In order to receive emails, your smtp server address should be made available somewhere. Two records should be added to your DNS records. Let us pretend that we want to receive emails at *@subdomain.domain.com:

  • First an MX record: subdomain.domain.com MX 10 mxsubdomain.domain.com. This means that the mail server for addresses like *@subdomain.domain.com will be mxsubdomain.domain.com.
  • Then an A record: mxsubdomain.domain.com A the.ip.address.of.your.Node-Mailin.server. This tells at which ip address the mail server can be found.

You can fire up Node-Mailin (see next section) and use an smtp server tester to verify that everything is correct.

Using Node-Mailin

From the command line

Install Node-Mailin globally.

sudo npm install -g node-mailin

Run it, (addtionnal help can be found using node-mailin --help). By default, Node-Mailin will listen on port 25, the standard smtp port. you can change this port for testing purpose using the --port option. However, do not change this port if you want to receive emails from the real world.

Ports number under 1000 are reserved to root user. So two options here. Either run Node-Mailin as root:

sudo node-mailin --port 25

Or, prefered choice, use something like authbind to run Node-Mailin with a standard user while still using port 25. Here comes a tutorial on how to setup authbind. In this case, do something like:

authbind --deep node-mailin --port 25

and make sure that your user can write to the log file.

At this point, Node-Mailin will listen for incoming emails, parse them, Then you can store them wherever you want.

Gotchas
  • error: listen EACCES: your user do not have sufficients privileges to run on the given port. Ports under 1000 are restricted to root user. Try with sudo.
  • error: listen EADDRINUSE: the current port is already used by something. Most likely, you are trying to use port 25 and your machine's mail transport agent is already running. Stop it with something like sudo service exim4 stop or sudo service postfix stop before using Node-Mailin.
  • error: Unable to compute spam score ECONNREFUSED: it is likely that spamassassin is not enabled on your machine, check the /etc/default/spamassassin file.
  • node: command not found: most likely, your system does not have node installed or it is installed with a different name. For instance on Debian/Ubuntu, the node interpreter is called nodejs. The quick fix is making a symlink: ln -s $(which nodejs) /usr/bin/node to make the node command available.
  • Uncaught SenderError: Mail from command failed - 450 4.1.8 <[email protected]>: Sender address rejected: Domain not found: The smtpOption disableDNSValidation is set to false and an email was sent from an invalid domain.

Embedded inside a node application

Install node-mailin locally.

sudo npm install --save node-mailin

Start the node-mailin server and listen to events.

const nodeMailin = require("node-mailin");

/* Start the Node-Mailin server. The available options are:
 *  options = {
 *     port: 25,
 *     logFile: '/some/local/path',
 *     logLevel: 'warn', // One of silly, info, debug, warn, error
 *     smtpOptions: { // Set of options directly passed to simplesmtp.createServer(smtpOptions)
 *        SMTPBanner: 'Hi from a custom Node-Mailin instance',
 *        // By default, the DNS validation of the sender and recipient domains is disabled so.
 *        // You can enable it as follows:
 *        disableDNSValidation: false
 *     }
 *  };
 * parsed message. */
nodeMailin.start({
  port: 25
});

/* Access simplesmtp server instance. */
nodeMailin.on("authorizeUser", function(connection, username, password, done) {
  if (username == "johnsmith" && password == "mysecret") {
    done(null, true);
  } else {
    done(new Error("Unauthorized!"), false);
  }
});

/* Event emitted when the "From" address is received by the smtp server. */
nodeMailin.on('validateSender', async function(session, address, callback) {
    if (address == '[email protected]') { /*blacklist a specific email adress*/
        err = new Error('You are blocked'); /*Will be the SMTP server response*/
        err.responseCode = 530; /*Will be the SMTP server return code sent back to sender*/
        callback(err);
    } else {
        callback()
    }
});

/* Event emitted when the "To" address is received by the smtp server. */
nodeMailin.on('validateRecipient', async function(session, address, callback) {
    console.log(address) 
    /* Here you can validate the address and return an error 
     * if you want to reject it e.g: 
     *     err = new Error('Email address not found on server');
     *     err.responseCode = 550;
     *     callback(err);*/
    callback()
});

/* Event emitted when a connection with the Node-Mailin smtp server is initiated. */
nodeMailin.on("startMessage", function(connection) {
  /* connection = {
      from: '[email protected]',
      to: '[email protected]',
      id: 't84h5ugf',
      authentication: { username: null, authenticated: false, status: 'NORMAL' }
    }
  }; */
  console.log(connection);
});

/* Event emitted after a message was received and parsed. */
nodeMailin.on("message", function(connection, data, content) {
  console.log(data);
  /* Do something useful with the parsed message here.
   * Use parsed message `data` directly or use raw message `content`. */
});

nodeMailin.on("error", function(error) {
  console.log(error);
});
Rejecting an incoming email

You can reject an incoming email when the validateRecipient or validateSender event gets called and you run the callback with an error (Can be anything you want, preferably an actual SMTP server return code)

nodeMailin.on('validateSender', async function(session, address, callback) {
    if (address == '[email protected]') {         /*blacklist a specific email adress*/
        err = new Error('Email address was blacklisted'); /*Will be the SMTP server response*/
        err.responseCode = 530;             /*Will be the SMTP server return code sent back to sender*/
        callback(err);                      /*Run callback with error to reject the email*/
    } else {
        callback()                          /*Run callback to go to next step*/
    }
});
Events
  • startData (connection) - DATA stream is opened by the client.
  • data (connection, chunk) - E-mail data chunk is passed from the client.
  • dataReady (connection, callback) - Client has finished passing e-mail data. callback returns the queue id to the client.
  • authorizeUser (connection, username, password, callback) - Emitted if requireAuthentication option is set to true. callback has two parameters (err, success) where success is a Boolean and should be true, if user is authenticated successfully.
  • validateSender (connection, email, callback) - Emitted if validateSender listener is set up.
  • senderValidationFailed (connection, email, callback) - Emitted if a sender DNS validation failed.
  • validateRecipient (connection, email, callback) - Emitted if validateRecipients listener is set up.
  • recipientValidationFailed (connection, email, callback) - Emitted if a recipient DNS validation failed.
  • close (connection) - Emitted when the connection to a client is closed.
  • startMessage (connection) - Connection with the Node-Mailin smtp server is initiated.
  • message (connection, data, content) - Message was received and parsed.
  • error (error) - And Error Occured.

Todo

webhooks.

Docs: StackFame Tech Blog

Credits

  • Postman image copyright Charlie Allen.
  • Heavily Inspired by mailin NPM Module.