Visiting your forum now, it appears to be working fine. Are there still issues on your end? I'll be monitoring the status. I can't reproduce the issue. It happens occasionally. I always access it via https://forum.c4d.space/ and this is the URL in config.json

@crazycells It does seem like package updates don't always update nbbpm... I will investigate.

You can run git cherry-pick 74aa12c95b2acd3dab01b283c33eb24a358411aa to get it.

Great, the posts works. Thank you!

You have to remove our comment out the assets location block. It may be possible to just exclude uploads, but you'll need to research the nginx syntax for that yourself.

@aleksei if you change the setting I said then new users will by default automatically be notified when replies are made to any topic they post. There's a different setting for if you want to be notified about replied to a topic you replied to. Again: you can configure the defaults for user settings in the ACP. New users will automatically be assigned the settings you select there. There's no way to make people be notified about every reply to every topic even if it isn't their topic or they didn't reply to it.

Works fine in latest firefox.

Apart from the suggested - is there another, more user-friendly, solution to achieve this?

I've found what was the problem: in my SendGrid account there was Link Branding enabled. But that's little bit strange because it was enabled before moving to the new server and it worked fine. [image: 1622823817033-b2e508e4-4bbf-4212-aee6-02b14cea34b5-image.png]

@antosik great, thank you!

@pitaj Also confirmed. I built a NodeBB instance for someone this morning and used the exact same process described here.

Obfuscating the email address does not raise the bar much as bot scrappers and ai will only continue to "progress". So we're left with encoding. Thankfully, at this juncture at least, most scappers are either not onto this or don't care since since a fringe case? Whatever. Still no magic bullet. But maybe best of the low hanging fruit options since should be easy peasy to code. Trying to mitigate email abuse is a noble goal. We just need to actually "game it out" cuz that is what this all boils down to for the AI hotshots. Else otherwise all you got is purely psychological protection...., a.k.a. PPP. Which is not a bad thing. If/when it's you're only thing. But.. just sayin.... stuff happens on the sharp end.

@aleksei Sounds like potentially a cool idea. But also potential for abuse. For e.g. many forum admins invest significant effort to foil file scrapers, etc. and this could facilitate/exacerbate. Maybe mitigated to some degree by permission restrictions to logged in users but..... then the bots just create a sock puppet account. Another potential issue: long running threads sporting hundreds of images, etc. How to display? Could be a UX conundrum, eh? Hmmmm... Still could be interesting for some situations. Not a dev but will hazard a guess that this might should be a plugin rather than core front end function as you suggest. Sorry I cannot offer more targeted insights.

@baris, great, thank you.

I've got the point. Thanks for all the help.

Thanks for the reply, @julian! Yes, I've tried using "ns-" plugin as well, but I had even less luck with it: it even doesn't show in the "Plugins" dropdown menu (cannot access plugin settings page). you can open an issue on their issue tracker. Are you talking about the Github issues section? Or there is another place where I can post it? P.S. The issue with the ns-embed on Github: https://github.com/NicolasSiver/nodebb-plugin-ns-embed/issues/29

Ok, the problem was solved. But I'm not sure how exactly. After I wrote this post I noticed that the latest version of NodeBB is 1.16.x. But while upgrading the forum i switched to 1.15.x branch (I thought that was the latest). After that, I used ./nodebb upgrade command. Maybe this was the issue? Maybe, I switched to the previous version branch, but installed the latest version of files with the "upgrade" command? — I don't really know. But when I switched to 1.16.x and upgraded the forum again, then it worked as expected. The forum now works fine.

@oplik0 the SMTP didn't work either. But thank you very much for pointing at the other services! I've just tried SendGrid and it worked perfectly from the 1st attempt.