agnos.is Forums

@shraga100 said in All NodeBB Emails Using Gmail Service Landing in Spam Folder:
> Hey everyone,
> I've recently set up my NodeBB forum and I'm having a really frustrating issue with the email system.
> Basically, I've configured NodeBB to send registration emails and updates using my Gmail account (with an "app password" for authentication). I left all the email templates with their default settings thinking they'd work fine out of the box.

If you are using a regular GMail type account ([email protected]) that is not unexpected and something you will have no control over. To get best delivery when using a Gmail related account, you are going to need to be using their Google Workspace offering ( a paid offering) in which you set up accounts for each user you need to use for a domain (your noreply address, a user address and then an admin address which is already around $22). I found that to be rather expensive and ended up instead setting up a MailCow-Dockerized instance on a VPS and use it for all my NodeBB instances. I get good delivery since the VPS provider I run it on has a clean IP for that instance and overall their IP range is not blocked (which is surprising since they are not a high dollar VPS provider).

I have a rather "limited" thread going on a site that I doubt will get any traction, but you are welcome to check out what I have relayed. And if interested I don't mind extending help there.

https://redneckhost.com/topic/12/preferred-precompiled-mta-package

@eeeee said in All NodeBB Emails Using Gmail Service Landing in Spam Folder:
> Its been the bain of my life!
> Ive said it before, Emails is the biggest issue with nodebb
>
> If the Admin panel menu could be reworked somehow to make it clearer / work better it would massively help nodebbs adoptance. Because people have given up with nodebb because of it.

Email is email is email.. does not really depend on what script you are using. The "gotchas" on my Xenforo install are much the same as they are on my NodeBB or Discourse installs. An knowledge of email configuration for use on a website is a must. It is not the same as setting up a personal email account to send from your desktop or phone.
There is a wealth more involved... DMARC, SPF, DKIM just to name a few.

Are you by chance using an email provider with a set user account@domain specific to them (like Hotmail or Google) and then using a different domain address for your website?
Not unusual if so as most do not allow relaying other domains through an account unless it is specifically allowed.

@xiaoye said in How to modify the "url" item in config.json?:
> I found the config.json in /opt/config, but I encountered the following problems when I edited it.
>

unusual, nano or vi is normally installed on most versions of linux.
odds are you need to install it then if it is not showing up.

Debian/Ubuntu base system
sudo apt install nano
or
sudo apt install vim

for Redhat based
sudo dnf install nano
or
sudo dnf install vim

@CWSmith said in New Forum on same Server Bad Gateway:

> Apparently I was missing a comma on the port entry... Lovely.

I run 3 sites on a small Contabo VPS using nginx as the proxy... and it was fun getting it all figured out. Like you, I had one site that simply did not want to play well, and it turned out to be missing comma.

@eeeee said in Is a Xenforo-like Resource Manager possible?:
> but on topic of you just having set up a nodebb instance. Which email service did you use (for nodebb to send out emails?)
> As this is, and has been, my biggest challenge with nodebb; Im wondering how all the new joiners to Nodebb are getting on with that aspect, and which mail client they are using?!

Not them, but I have been using ZoHo free level. They allow you to send via SMTP on the free plan but you cannot use POP3/IMAP to check email unless you are on a paid tier, so you have to log into their web based interface to check mail. But for what I needed it for, which is only sending out emails it works out great.

Have you checked your error logs?
Both in NodeBB and if you are using nginx (or apache) as a proxy in them?

If you are just setting the site up and have no content, have you tried redoing it again following the guide?