Skip to content

Nodebb and emails

Solved Configure
27 2 3.7k 1
  • what version of nodebb is this site on now? Theres a bug that when I post it remains blank. If I reload page what I type shows!

  • what version of nodebb is this site on now? Theres a bug that when I post it remains blank. If I reload page what I type shows!

    @Panda that’s a css issue I need to fix. Nothing major.

  • @phenomlab Ive put a plea of Nodebb site for a response to my many threads on this.
    Im not overstating it when I say people have left nodebb because of the same headache

    @Panda said in Nodebb and emails:

    Im not overstating it when I say people have left nodebb because of the same headache

    It’s going to be something simple. PM me the details of your site, and also the details for your fastmail account and I’ll get it to work.

    I’ll need your fastmail login and admin access to your forum.

  • OK, after taking a look at this, I’ve done the following

    1. Set your nodebb instance to use custom smtp and send via smtp.fastmail.com
    2. Save and test

    I now get the error

    Invalid login: 535 5.7.0 Sorry, you need to create an app password to use this service. Please see fastmail.com/help for more details.
    

    This means you need to configure an app inside fastmail to send emails.

    After you’ve done this, it should work

  • OK, after taking a look at this, I’ve done the following

    1. Set your nodebb instance to use custom smtp and send via smtp.fastmail.com
    2. Save and test

    I now get the error

    Invalid login: 535 5.7.0 Sorry, you need to create an app password to use this service. Please see fastmail.com/help for more details.
    

    This means you need to configure an app inside fastmail to send emails.

    After you’ve done this, it should work

    @phenomlab ok thanks will try with app password
    I wonder why it needed custom setup

  • @phenomlab ok thanks will try with app password
    I wonder why it needed custom setup

    @Panda likely because the predefined settings are out of date. Realistically, nodebb devs can’t possibly maintain correct settings for mail services they do not control.

  • Pandaundefined Panda has marked this topic as solved on
  • Finally it works, thanks.
    I had to regenerate the app password on fastmail, and the test email send is working.

    Out of interest, in your custom set up of fastmail, how did you know to pick SMPT port 465?

  • Finally it works, thanks.
    I had to regenerate the app password on fastmail, and the test email send is working.

    Out of interest, in your custom set up of fastmail, how did you know to pick SMPT port 465?

  • phenomlabundefined phenomlab has marked this topic as solved on
  • Follow up question:
    Re this past comment on NodeBB
    “There are three ways to send emails from NodeBB:
    Emailer plugin. (Like sendgrid). These plugins allow you to use email distribution services like Sendgrid, MailChimp, etc to send out emails. This helps about issues of spam filtering and such, because it’s their email servers handling all of that. These plugins contact the email service via http and then the service sends your emails out.
    SMTP transport. This is built into NodeBB. It is only used if you don’t have an emailer plugin active and you enable “Enable SMTP transport” (previously “Use an external server to send emails”) in the email settings. The SMTP transport allows you to either pick from a list of known services (provided by the underlying module nodemailer) or to provide custom settings yourself. It contacts the server via SMTP and then the SMTP server sends your your emails.”

    Im still confused about which of these methods is best in theory
    When you use an internal post fix server does this use (1) Emailer plugin or (2) SMTP?

  • Follow up question:
    Re this past comment on NodeBB
    “There are three ways to send emails from NodeBB:
    Emailer plugin. (Like sendgrid). These plugins allow you to use email distribution services like Sendgrid, MailChimp, etc to send out emails. This helps about issues of spam filtering and such, because it’s their email servers handling all of that. These plugins contact the email service via http and then the service sends your emails out.
    SMTP transport. This is built into NodeBB. It is only used if you don’t have an emailer plugin active and you enable “Enable SMTP transport” (previously “Use an external server to send emails”) in the email settings. The SMTP transport allows you to either pick from a list of known services (provided by the underlying module nodemailer) or to provide custom settings yourself. It contacts the server via SMTP and then the SMTP server sends your your emails.”

    Im still confused about which of these methods is best in theory
    When you use an internal post fix server does this use (1) Emailer plugin or (2) SMTP?

    @Panda it will use SMTP. In all cases, I never use any plugin to send email. I’ll always send it raw.


Did this solution help you?
Did you find the suggested solution useful? Support 💗 Sudonix with a coffee
If your organisation needs deeper expertise around infrastructure, security, or technology leadership, learn more about Phenomlab Ltd. Many of the deeper technical guides behind Sudonix are published there.

Related Topics
  • Opening links in nodebb widget

    Solved Configure nodebb
    6
    4 Votes
    6 Posts
    2k Views
    A more efficient way of including this would be to not over complicate it and leverage a standard iframe (providing the CSP headers of the remote site permit this) like below <iframe src="https://www.classmarker.com/online-test/start/?quiz=gag66aea7922f0a5" width="700" height="800"></iframe> This works first time every time on your site as intended.
  • Nodebb design

    Solved General nodebb
    2
    1 Votes
    2 Posts
    859 Views
    @Panda said in Nodebb design: One negative is not being so good for SEO as more Server side rendered forums, if web crawlers dont run the JS to read the forum. From recollection, Google and Bing have the capability to read and process JS, although it’s not in the same manner as a physical person will consume content on a page. It will be seen as plain text, but will be indexed. However, it’s important to note that Yandex and Baidu will not render JS, although seeing as Google has a 90% share of the content available on the web in terms of indexing, this isn’t something you’ll likely lose sleep over. @Panda said in Nodebb design: The “write api” is preferred for server-to-server interactions. This is mostly based around overall security - you won’t typically want a client machine changing database elements or altering data. This is why you have “client-side” which could be DOM manipulation etc, and “server-side” which performs more complex operations as it can communicate directly with the database whereas the client cannot (and if it can, then you have a serious security flaw). Reading from the API is perfectly acceptable on the client-side, but not being able to write. A paradigm here would be something like SNMP. This protocol exists as a UDP (UDP is very efficient, as it is “fire and forget” and does not wait for a response like TCP does) based service which reads performance data from a remote source, thus enabling an application to parse that data for use in a monitoring application. In all cases, SNMP access should be “RO” (Read Only) and not RW (Read Write). It is completely feasible to assume complete control over a firewall for example by having RW access to SNMP and then exposing it to the entire internet with a weak passphrase. You wouldn’t do it (at least, I hope you wouldn’t) and the same ethic applies to server-side rendering and the execution of commands.
  • Composer options on nodebb

    Solved Configure nodebb
    8
    1
    3 Votes
    8 Posts
    1k Views
    @Panda You should be able to expose the CSS for these using F12 to get into console [image: 1686833368846-3591518c-e3a3-4ada-a43c-6b32a5e0359c-image.png] [image: 1686833399483-a2b8ed46-4157-4ff2-85f0-576543380107-image.png] That should then expose the element once selected [image: 1686833431032-89d9c545-a47a-40d1-98f4-80cf3b958e8f-image.png] Here’s the below CSS you need based on the screenshot provided. .composer .formatting-bar .formatting-group li[data-format="picture-o"], .composer .formatting-bar .formatting-group li[data-format="spoiler"] { display: none; }
  • NodeBB v3 Android Problem

    Solved Configure nodebb android
    4
    4 Votes
    4 Posts
    889 Views
    thank you fixed.
  • NodeBB: Consent page

    Solved Configure nodebb consent
    16
    4 Votes
    16 Posts
    4k Views
    @DownPW I still do not see any issues.
  • 11 Votes
    14 Posts
    3k Views
    @dave1904 excellent news. Thanks for the feedback
  • Configure SMTP for Nodebb

    Solved Configure
    14
    5 Votes
    14 Posts
    3k Views
    @marusaky based on the work completed thus far (in relation to PM exchanges), I’m going to mark this completed. Sending email from the server itself works fine without issue, and DNS appears to be clean (valid SPF, DMARC, and DKIM records). It appears that only Gmail marks incoming messages from your domain as spam - perhaps because of the domain age, which there is nothing we can do to prevent this. Mail delivery to all other domains appears to work fine in al of my tests.
  • is "night mode" shifting the forum several pixels up?

    Solved Configure nodebb
    8
    4 Votes
    8 Posts
    2k Views
    @crazycells hmm. Good point. I actually use my own version of the dark mode plugin, so not entirely sure. However, I think the CSS is probably the same. I’m not at my PC currently but can check and advise later.