EDITED by psychobunny:
For 0.4x compatibility please use this fork for now, until @BarveyHirdman can merge my PR
npm install git://github.com/psychobunny/nodebb-plugin-emailer-local

Yesterday I was in great need of the option to send emails via SMTP from NodeBB so I hacked a quick plugin for it.

I decided to make it official and extend it to a point it will be actually useful. I've already published the first version to NPM so you can get it, try it and make suggestions in the repo's issue tracker.

The installation is basically

cd path/to/nodebb && npm install nodebb-plugin-emailer-local

Then enable the plugin in the administrator panel and configure it in its own little section.

Further improvements to do (suggestions more than welcome):

*Use of services (as the plugin uses Nodemailer, I can't see any difficulties in achieving that)
*More options (Secured connection, DKIM signing, maybe SMTP connection pool)

The repository: http://github.com/AlfredDobradi/nodebb-plugin-emailer-local
NPM page: https://npmjs.org/package/nodebb-plugin-emailer-local

This is the first NPM package and NodeBB I ever published so if I left something out, please tell.

@kevin I'm not exactly sure what you're trying to do. When you run forever start app.js it starts a daemon running in the background. You don't have to run node app again, you can close the terminal, the forever process will take care of your NodeBB.

Also if you're logged in with root (which I'd not encourage) you don't have to use sudo, forever start app.js is fine.

@kevin http://californiamotorcycleforum.com/

@kevin could you paste your public/config.json content here? Maybe manually configuring the socket.address and socket.port values would help.

@kevin just an idea, which actually helped me:

Edit your public/config.json file:

{
    "relative-path": "",
    "websocket": {
        "address": "198.199.96.7",
        "port": "4567"
    }
}

I'm not sure but maybe it's possible the websocket connection goes to some place it's not getting picked up.

@julian well for now I basically just copied the Mailgun plugin and changed the values to save a minimal SMTP config and wired nodemailer in, but I'll get to it and all kinds of wizardry. (Like DKIM, popular services, anything possible with Nodemailer)

I'm stuck to be honest, I'll try and think about this some more when I get home.

@kevin you shouldn't edit /etc/nginx/sites-enabled directly.

The normal flow of enabling sites is

• nano /etc/nginx/sites-available/<site-name>
• write config
• ln -s /etc/nginx/sites-available/<site-name> /etc/nginx/sites-enabled/<site-name>

This creates a symbolic link to the file in sites-available. Anyway, the default config is usually in the default file, other than that a good convention can be <subdomain>.<domain>, or in your case just californiamotorcycleforum.com

@skaughtx0r yeah sometimes it's the same for me, not sure what causes it. But yeah, if it doesn't work, you can just copy it. It's just more consistent if you edit the file in sites-available and not the one in sites-enabled directly.

@kevin you can upgrade Nginx to the latest version this way (as you have to use backports

echo deb http://ftp.debian.org/debian wheezy-backports main contrib non-free >> /etc/apt/sources.list
apt-get update
aptitude -t wheezy-backports install nginx nginx-common nginx-full

Maybe nginx-full is enough, I did it this way just to be sure.