Hello, I like discourse's achievement system which automatically awards users with points and badges upon completing certain actions. Even just browsing the forum the system awards them.

NodeBB has a plugin similar to this as seen here: https://community.nodebb.org/topic/4397/nodebb-plugin-ns-awards-ns-awards-give-medals

The problem is the plugin is outdated and no longer works on the latest nodeBB.

I think a feature like this is extremely important for user experience and engagement. When people are awarded for something they tend to repeat the behavior so this will help with user retention.

Hi, I would like to display a scrollbar to the right of topics. NodeBB already has the scrollbar but it's embedded in the pagination block in the bottom right corner.

I tried modifying the code in the scrollbar.tpl file (persona template) but it did not work which is not surprising since the code in there is just an HTML container.

Any help would be appreciated.

@nicolas Just wondering if you're planning on updating the plugin to work with the latest nodeBB version.

@pitaj Yes! That fixed it!

I'm assuming you're going to let the nodeBB dev team know about this, eh? Great job.

@vaulverin said in Email suddenly no longer works with SMTP Relay Google Workspace:

@emotion Yay, their email response gave me an idea to use "name" option in nodemail configuration, and it worked!
I had the same problem, emails had been correctly sent but a week ago or so they stopped, in logs i saw that 421, "4.7.0" error.
Here is what i use as transport configuration now

{
    "name": "your-domain-name.com",
    "host" : "smtp-relay.gmail.com",
    "port" : 465,
    "secure": true,
    "pool": true
  },

Thank you!

Awesome, glad you got it to work.

@theopenem said in Email suddenly no longer works with SMTP Relay Google Workspace:

@emotion said in Email suddenly no longer works with SMTP Relay Google Workspace:

The problem with letting postfix relay the mail is that it lacks DKIM, DMARC, and SPF records which makes your emails more likely to end up in the spam folder.

I'm using postfix to relay all mail to gmail. It ends up being the same thing as if you set the relay in NodeBB.

How many sites do you have running on the server? If it's just 1 then yeah postfix relay will be the same as a direct relay. But if you have multiple sites then the mailing domain and the return path will be the FQDN. At least that's how it is with my configuration.

If you have multiple sites and they're all being mailed by the sending domain can you share your configuration please?

@pitaj said in Email suddenly no longer works with SMTP Relay Google Workspace:

@emotion a restart of your forum would eliminate the issue, so it's highly unlikely that issue is causing this.

As you said you'd likely see a different error if it was falling back to sendmail.

The Flarum forum also has 0 active users, but again with the exact same SMTP relay settings it sends emails just fine.

I don't know and this is extremely frustrating. I wish I could help but you might need to ask people with more expertise, try Stack Overflow or the Nodemailer GitHub issues. I'll see if I can write up a minimal reproduction example for you to try (removing NodeBB from the picture) so you can post there.

Thanks, that's a good idea, I might do that.

@gotwf said in Email suddenly no longer works with SMTP Relay Google Workspace:

might try pinging @scottalanmiller. i am recouperating from hand surgery & a bit challenged at present.

maybe try test goog's smtp relays manually from cli, e.g.:

Postfix SASL Howto

(www.postfix.org)

Edit: in case not clear, I meant to test from cli on the respective server. If that all works, then you've isolated to nodebb, no? which may well already be the case but still nice to have confirmation and the real time responses from gsmtp server might proof informative. good luck o/

Well, Flarum works fine with it. Still, I tested to see if telnet would connect with it and it does:

$ telnet smtp-relay.gmail.com 587
Trying 2607:f8b0:400d:c03::1c...
Connected to smtp-relay.gmail.com.
Escape character is '^]'.
220 smtp-relay.gmail.com ESMTP v24sm193634pjt.16 - gsmtp

@theopenem said in Email suddenly no longer works with SMTP Relay Google Workspace:

I had the same thing happen. Emails have been working fine when using the gmail smtp server for months. Then a few days ago it stopped working with the same error as mentioned above. I have a wordpress site on the same server as nodebb with the same relay settings and it continues to work fine. It also works fine when using telnet from that same server. NodeBB is the only thing that seems to be effected. I solved the problem by disabling "Use an external email server to send emails" and just letting postfix relay the mail for me. Just thought I'd share.

How are you connecting WordPress to smtp-relay.gmail.com? Are you using a plugin?

The problem with letting postfix relay the mail is that it lacks DKIM, DMARC, and SPF records which makes your emails more likely to end up in the spam folder. Also, if you have multiple sites running on the same server then postfix mails every email from the primary domain, usually in /etc/mailname, which essentially spoofs emails and again makes it more likely to end up in spam.

In any case, I contacted Google Workspace support on Friday and chatted with them for over 2 hours about this issue. They couldn't figure it out and kept insisting it was a denial of service issue, but they didn't make it clear if it was on my end or theirs.

They sent me an email today:

After consulting your case related to the SMTP relay issue and also verifying similar cases, it appears that the issue is highly related to the Denial of Service as we discussed during our chat interaction, probably, the system detected a massive email delivery from the previous set up causing this error to appear.

As suggested, it will be necessary to declare your domain at the HELO command, from the tool that you are using adding your domain name so our system will be able to complete the authentication, it is strongly recommended to contact the app developer or their community forum to see if there's another way for you to add this command.

In case is needed, you can visit the following Help Center article for more information about setting the SMTP relay, it will come in handy https://support.google.com/a/answer/2956491

It was a pleasure to assist you. I'll keep this case open for the next three business days so you can let me know if additional assistance is needed. Once the case closes, you can reply in the next 30 days to reopen it. Have a nice day!

Is this currently possible with nodeBB?

@pitaj said in Email suddenly no longer works with SMTP Relay Google Workspace:

@emotion I don't really know how to help you either. I am not an expert on SMTP or Google Workspace. Does using the IP instead of the domain give you the same error?

Maybe you're being rate limited because of too many emails sent from the same server? Maybe try the debug steps here: https://glockapps.com/blog/remove-ip-address-gmail-blacklist/

Tried both IP addresses listed here, 64.233.162.28 and 74.125.195.28. Both appear to connect to the SMTP server but again give the same error.

TBH, my forum has 0 active users lol. The Flarum forum also has 0 active users, but again with the exact same SMTP relay settings it sends emails just fine. So it can't be rate limitation.

@baris said in Email suddenly no longer works with SMTP Relay Google Workspace:

Is this related? https://github.com/NodeBB/NodeBB/issues/9223

Not sure, but I installed v1.12.1 just to test it out because I know in the past it used to work fine. It's the same error, only this time nodeBB says it sent it successfully but the logs say otherwise:

2021-01-30T01:13:38.241Z [5835/15098] - error: Server terminates connection. response=421 4.7.0 Try again later, closing connection. (EHLO) b25sm1995991oot.16 - gsmtp: 421 4.7.0 Try again later, closing connection. (EHLO) b25sm1995991oot.16 - gsmtp {"code":"ECONNECTION","response":"421 4.7.0 Try again later, closing connection. (EHLO) b25sm1995991oot.16 - gsmtp","responseCode":421,"command":"EHLO"}

Why would it work with Flarum but not nodeBB?

Also, wouldn't nodeBB give me a different error if it was falling back to postfix? Regardless, I see that you've fixed it in the latest commit. How do I upgrade my forum to it?

@pitaj You're right, digest fails silently. And yes it does produce an error in the server log:

2021-01-29T10:12:00.592Z [4567/26001] - error: [user/jobs] Could not send digest email
[emailer.send] Error: Server terminates connection. response=421 4.7.0 Try again later, closing connection. (EHLO) w12sm600011oor.23 - gsmtp: 421 4.7.0 Try again later, closing connection. (EHLO) w12sm600011oor.23 - gsmtp
    at SMTPConnection._actionEHLO (/var/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:1229:27)
    at SMTPConnection._processResponse (/var/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:932:20)
    at SMTPConnection._onData (/var/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:739:14)
    at Socket.SMTPConnection._onSocketData.chunk (/var/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:189:44)
    at Socket.emit (events.js:198:13)
    at addChunk (_stream_readable.js:288:12)
    at readableAddChunk (_stream_readable.js:269:11)
    at Socket.Readable.push (_stream_readable.js:224:10)
    at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

All the other options produce the same error:

2021-01-29T10:18:38.846Z [4567/26001] - error: admin.email.test
Error: Server terminates connection. response=421 4.7.0 Try again later, closing connection. (EHLO) g2sm1514993otp.7 - gsmtp: 421 4.7.0 Try again later, closing connection. (EHLO) g2sm1514993otp.7 - gsmtp
    at SMTPConnection._actionEHLO (/var/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:1229:27)
    at SMTPConnection._processResponse (/var/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:932:20)
    at SMTPConnection._onData (/var/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:739:14)
    at Socket.SMTPConnection._onSocketData.chunk (/var/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:189:44)
    at Socket.emit (events.js:198:13)
    at addChunk (_stream_readable.js:288:12)
    at readableAddChunk (_stream_readable.js:269:11)
    at Socket.Readable.push (_stream_readable.js:224:10)
    at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

I have no idea how to even approach fixing this problem.

@pitaj Digest. Just tried it again and it says it sent it successfully. But nothing arrived in my inbox nor spam folder.

I tried the other options and all of them, except digest, are giving me the same 421 4.7.0 error. This is very strange.

Tried it again today and when I send a test email it says it was sent successfully but it doesn't arrive in my inbox.

@pitaj said in Email suddenly no longer works with SMTP Relay Google Workspace:

@emotion I've seen some people say it's related to IPv6. Try replacing smtp-relay.gmail.com with the ip address instead: 64.233.162.28

Thanks, tried that and it said successful upon sending a test email but again it doesn't arrive in my inbox.

@gotwf said in Email suddenly no longer works with SMTP Relay Google Workspace:

@emotion The second message condirms the 421 Error Code of the first. Checking your nearest RFC:

The service is unavailable due to a connection problem: it may refer to an exceeded limit of simultaneous connections, or a more general temporary problem.

@pitaj said in Email suddenly no longer works with SMTP Relay Google Workspace:

@emotion I've seen some people say it's related to IPv6. Try replacing smtp-relay.gmail.com with the ip address instead: 64.233.162.28

Why the 64.x address? After some quick drillin' I syspect this maybe resolves to various:

<kvg@loon:~>% drill smtp-relay.gmail.com
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 59360
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; smtp-relay.gmail.com. IN A

;; ANSWER SECTION:
smtp-relay.gmail.com. 300 IN A 74.125.195.28

I suspect that the Goog's relays are simply a bit constipated. Give them some time. In the meantime, are your "failed" messages relegared to a mail spool, to try, try again, the mail must get thru? Or are they a one and done kind of deal?

My $0.02. Proll'y half-baked as well.... Have fun! o/

I think they're a one and done deal. How do I check though?

I tried your IP address and it's the same error.

Odd, just a few moments ago I had no error when sending a test email but now I get that same 421 4.7.0 error.

Disabling pooled connections doesn't seem to make a difference.

If I add my Workspace admin account and an app password, I can send emails. However, the mailing domain and the return path is the domain of the Workspace admin account. I don't want this. What's more is it's missing DKIM, SPF, and DMARC.

SMTP relay fixes all these problems and lets the forum domain be the sender along with its own DKIM, SPF, and DMARC records.

Hi, I've setup nodebb to send emails via Google Workspace SMTP relay and it was working fine until just a few days ago. I have no idea what happened, but now when I send a test email from the admin page I get this error:

ERROR
Server terminates connection. response=421 4.7.0 Try again later, closing connection. (EHLO) s22sm961094vkm.4 - gsmtp: 421 4.7.0 Try again later, closing connection. (EHLO) s22sm961094vkm.4 - gsmtp

According to the Google docs this error means:

421, "4.7.0", Try again later, closing connection. This usually indicates a Denial of Service (DoS) for the SMTP relay at the HELO stage.

Not sure what that means but I have a Flarum forum running on the same server with the same SMTP relay setup for Google Workspace Gmail and it works fine.

My settings:

Custom Service
SMTP Host: smtp-relay.gmail.com
SMTP Port: 587
Connection security: StartTLS

Any help would be appreciated.

@pitaj

The plugin was indeed in the dependencies section even though it was not installed on my nodeBB instance, weird.

Removing it has fixed the error. Thank you so much for your help

Here's how the package.json file looked like:

{
  "name": "nodebb",
  "license": "GPL-3.0",
  "description": "NodeBB Forum",
  "version": "1.16.1",
  "homepage": "http://www.nodebb.org",
  "repository": {
    "type": "git",
    "url": "https://github.com/NodeBB/NodeBB/"
  },
  "main": "app.js",
  "scripts": {
    "start": "node loader.js",
    "lint": "npx eslint --cache ./nodebb .",
    "test": "npx nyc --reporter=html --reporter=text-summary npx mocha",
    "coverage": "nyc report --reporter=text-lcov > ./coverage/lcov.info",
    "coveralls": "nyc report --reporter=text-lcov | coveralls && rm -r coverage"
  },
  "husky": {
    "hooks": {
      "pre-commit": "npx lint-staged",
      "commit-msg": "npx commitlint -E HUSKY_GIT_PARAMS"
    }
  },
  "lint-staged": {
    "*.js": [
      "eslint --fix",
      "git add"
    ]
  },
  "dependencies": {
    "@adactive/bootstrap-tagsinput": "^0.8.2",
    "@nodebb/bootswatch": "3.4.2",
    "ace-builds": "^1.4.9",
    "archiver": "^5.0.0",
    "async": "^3.2.0",
    "autoprefixer": "10.2.0",
    "bcryptjs": "2.4.3",
    "benchpressjs": "2.4.0",
    "body-parser": "^1.19.0",
    "bootbox": "4.4.0",
    "bootstrap": "^3.4.1",
    "chart.js": "^2.9.3",
    "cli-graph": "^3.2.2",
    "clipboard": "^2.0.6",
    "colors": "^1.4.0",
    "commander": "^6.0.0",
    "compare-versions": "3.6.0",
    "compression": "^1.7.4",
    "connect-ensure-login": "^0.1.1",
    "connect-flash": "^0.1.1",
    "connect-mongo": "3.2.0",
    "connect-multiparty": "^2.2.0",
    "connect-pg-simple": "^6.1.0",
    "connect-redis": "5.0.0",
    "cookie-parser": "^1.4.5",
    "cron": "^1.8.2",
    "cropperjs": "^1.5.6",
    "csurf": "^1.11.0",
    "daemon": "^1.1.0",
    "diff": "^5.0.0",
    "express": "^4.17.1",
    "express-session": "^1.17.0",
    "express-useragent": "^1.0.13",
    "graceful-fs": "^4.2.3",
    "helmet": "^4.0.0",
    "html-to-text": "6.0.0",
    "ipaddr.js": "^2.0.0",
    "jquery": "3.5.1",
    "jquery-deserialize": "2.0.0-rc1",
    "jquery-form": "4.3.0",
    "jquery-serializeobject": "1.0.0",
    "jquery-ui": "1.12.1",
    "jsesc": "3.0.2",
    "json2csv": "5.0.5",
    "jsonwebtoken": "^8.5.1",
    "less": "^3.11.1",
    "lodash": "^4.17.15",
    "logrotate-stream": "^0.2.6",
    "lru-cache": "6.0.0",
    "material-design-lite": "^1.3.0",
    "mime": "^2.4.4",
    "mkdirp": "^1.0.4",
    "mongodb": "3.6.3",
    "morgan": "^1.10.0",
    "mousetrap": "^1.6.5",
    "nconf": "^0.11.0",
    "nodebb-plugin-composer-default": "6.5.5",
    "nodebb-plugin-dbsearch": "4.1.2",
    "nodebb-plugin-emoji": "^3.3.0",
    "nodebb-plugin-emoji-android": "2.0.0",
    "nodebb-plugin-gamification": "^1.0.1",
    "nodebb-plugin-markdown": "8.12.4",
    "nodebb-plugin-mentions": "2.13.6",
    "nodebb-plugin-question-and-answer": "^0.7.7",
    "nodebb-plugin-require": "0.0.6",
    "nodebb-plugin-seo": "^1.0.0",
    "nodebb-plugin-seo-slug-friendly": "0.0.8",
    "nodebb-plugin-seo-thread": "^0.1.10",
    "nodebb-plugin-soundpack-default": "1.0.0",
    "nodebb-plugin-spam-be-gone": "0.7.7",
    "nodebb-rewards-essentials": "0.1.4",
    "nodebb-theme-lavender": "5.0.17",
    "nodebb-theme-persona": "10.3.17",
    "nodebb-theme-slick": "1.3.7",
    "nodebb-theme-vanilla": "11.3.10",
    "nodebb-widget-essentials": "5.0.2",
    "nodemailer": "^6.4.6",
    "nprogress": "0.2.0",
    "passport": "^0.4.1",
    "passport-http-bearer": "^1.0.1",
    "passport-local": "1.0.0",
    "pg": "^8.0.2",
    "pg-cursor": "^2.1.9",
    "postcss": "8.1.10",
    "postcss-clean": "1.1.0",
    "promise-polyfill": "^8.1.3",
    "prompt": "^1.0.0",
    "redis": "3.0.2",
    "request": "2.88.2",
    "request-promise-native": "^1.0.8",
    "requirejs": "2.3.6",
    "rimraf": "3.0.2",
    "rss": "^1.2.2",
    "sanitize-html": "^2.0.0",
    "semver": "^7.2.1",
    "serve-favicon": "^2.5.0",
    "sharp": "0.27.0",
    "sitemap": "^6.1.0",
    "slideout": "1.0.1",
    "socket.io": "3.0.5",
    "socket.io-adapter-cluster": "^1.0.1",
    "socket.io-client": "3.0.5",
    "socket.io-redis": "6.0.1",
    "sortablejs": "1.10.2",
    "spdx-license-list": "^6.1.0",
    "spider-detector": "2.0.0",
    "textcomplete": "^0.17.1",
    "textcomplete.contenteditable": "^0.1.1",
    "timeago": "^1.6.7",
    "tinycon": "0.6.8",
    "toobusy-js": "^0.5.1",
    "uglify-es": "^3.3.9",
    "validator": "13.5.2",
    "visibilityjs": "2.0.2",
    "winston": "3.3.3",
    "xml": "^1.0.1",
    "xregexp": "^4.3.0",
    "zxcvbn": "^4.4.2"
  },
  "devDependencies": {
    "@apidevtools/swagger-parser": "10.0.2",
    "@commitlint/cli": "11.0.0",
    "@commitlint/config-angular": "11.0.0",
    "coveralls": "3.1.0",
    "eslint": "7.17.0",
    "eslint-config-airbnb-base": "14.2.1",
    "eslint-plugin-import": "2.22.1",
    "grunt": "1.3.0",
    "grunt-contrib-watch": "1.1.0",
    "husky": "4.3.6",
    "jsdom": "16.4.0",
    "lint-staged": "10.5.3",
    "mocha": "8.2.1",
    "mocha-lcov-reporter": "1.3.0",
    "nyc": "15.1.0",
    "smtp-server": "3.8.0"
  },
  "bugs": {
    "url": "https://github.com/NodeBB/NodeBB/issues"
  },
  "engines": {
    "node": ">=10"
  },
  "maintainers": [
    {
      "name": "Andrew Rodrigues",
      "email": "[email protected]",
      "url": "https://github.com/psychobunny"
    },
    {
      "name": "Julian Lam",
      "email": "[email protected]",
      "url": "https://github.com/julianlam"
    },
    {
      "name": "Barış Soner Uşaklı",
      "email": "[email protected]",
      "url": "https://github.com/barisusakli"
    }
  ],
  "nyc": {
    "exclude": [
      "src/upgrades/*",
      "test/*"
    ]
  }
}

@pitaj

Thanks, but it's the same error:

$ npm rm nodebb-plugin-seo-thread
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm ERR! code ENOVERSIONS
npm ERR! No valid versions available for nodebb-plugin-seo-thread

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/MY_USER/.npm/_logs/2021-01-10T04_45_16_534Z-debug.log

@julian Thanks for the reply. Yeah, I thought of doing that but there's no folder called nodebb-plugin-seo-thread in node_modules. There's a folder called nodebb-plugin-seo. I just moved it to a different directory and tried the upgrade command again.

Same thing, still results in an error about nodebb-plugin-seo-thread

How do I troubleshoot this problem?

I tried upgrading my nodebb instance to the latest version and followed the instructions in the nodebb documentation. I got an error with a plugin called "nodebb-plugin-seo-thread" which I don't remember installing tbh and now I can't run nodebb.

I tried running the command to uninstall the plugin but it results in the same error.

$ ./nodebb reset -p nodebb-plugin-seo-thread
Dependencies outdated or not yet installed.
Installing them now...

npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm ERR! code ENOVERSIONS
npm ERR! No valid versions available for nodebb-plugin-seo-thread

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/USER/.npm/_logs/2021-01-09T04_03_14_732Z-debug.log
Error installing dependencies!
message: Command failed: npm install --production
stdout: null
stderr: null
/var/www/emotionforums.com/nodebb/src/cli/package-install.js:81
                throw e;
                ^

Error: Command failed: npm install --production
    at checkExecSyncError (child_process.js:629:11)
    at Object.execSync (child_process.js:666:13)
    at Object.installAll (/var/www/emotionforums.com/nodebb/src/cli/package-install.js:72:9)
    at Object.<anonymous> (/var/www/emotionforums.com/nodebb/src/cli/index.js:60:18)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:692:17)

Any help would be appreciated.