SMTP timeout

Technical Support
  • Hello i got some error with * nodebb-plugin-emailer-local-bobo
    My configuration
    You are running NodeBB v1.1.0.
    You are up-to-date

    5/8 12:38 [8123] - info: Enabling 'trust proxy'
    5/8 12:38 [8123] - info: NodeBB is now listening on:
    5/8 12:38 [8123] - info: [plugins/spam-be-gone] Settings loaded
    5/8 12:39 [8123] - warn: [emailer.smtp] Unable to send `digest` email to uid 1!!
    5/8 12:39 [8123] - error: [plugins] filter:email.send,  Connection timeout
    5/8 12:40 [8123] - warn: [emailer.smtp] Unable to send `digest` email to uid 1!!
    5/8 12:40 [8123] - error: [plugins] filter:email.send,  Connection timeout ```
    root@.....# ls node_modules | grep emailer
    Do you know some good plugin or how to fix that thanks
  • What's local-bobo, and do you need it? NodeBB should send emails using local sendmail, out of the box.

    Either way, though, I'd recommend a third-party emailer via SendGrid, as they have a free plan.

  • After clean install on new server without apache
    Ubuntu 16.04 nignx my conf nginx -t is good.
    nodebb works as well
    but i never can sent any email with nodebb i was thinking we need some plugin for that.
    The sendmail executable could not be found, please ensure it is installed and executable by the user running NodeBB.
    That is without any plugin.

  • @Bastien you will either need sendmail installed on your server to be able to send email from local or use one of the available emailer plugins. Those third party emailer services do have some free plans.


Suggested Topics

  • 0 Votes
    4 Posts


    None in my /etc/nginx.conf but I have types_hash_max_size 2048;

    And I have ip_hash directives on my /etc/nginx/mywebsite.conf like the scaling redis official documentation :

    upstream io_nodes { ip_hash; server; server; server; }
  • 0 Votes
    24 Posts

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

    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.

    Moreover, you now have a mail spool for failed messages, access to meaningful log messages, ability to tweak and tune if necessary, etc. This is a big win. But maybe too much a pita for some. Until something breaks. 😜

    DKIM is lame. Search "DKIM considered bad". Here's one rant from ZDNet.

    Iirc (and it has been a while since I needed to read up cuz my stuff jfw....), SPF has no restrictions on number of different domains - just add the spf txt record to that domain. Then make sure the relay has a reverse dns entry - that does not have to be the same domain, just has to be.

    I was hoping for some better diagnostics, wh/is why I suggested the cli. Establishing an initial connection is easy. It is what comes next that is important and unfortunately OP did not see that bit thru. Why does not somebody test it, eh? I don't have any goog accts, nor do I want/need one, but it may prove illuminating?

    Just my $0.02.

    P.S.; Or maybe ptr is even easier than that for this use case: create a redirect to goog's? then goog worries about the nitty gritty for you. Like I said, been a while and shootin' from the hip. Double check the rfc, eh?

    Here's some DMARC spf resources for the bold and curious.

    P.P.S.; Geronimo, here ya' go. Big medicine!

    Primary domain sporting the smtp relay zone file:

    relaydomain.tld. IN TXT "v=spf1 ip4:yyy.yyy.yyy.yyz -all"

    otherdom.tld zone file:

    otherdom.tld. IN TXT "v=spf1 redirect=relaydom.tld"

    foodom.tld zone file:

    foodom.tld. IN TXT "v=spf1 redirect=relaydom.tld"

    anotherdom.tld zone file

    @ IN TXT "v=spf1 redirect=relaydom.tld"

    More than one way to do it, note the @ in second example there. Save typing but less explicit. Pick yer' poison.

    Then use a checker. I favor MXToolbox, but note the Goog has one specific for their stuff Google Admin Toolbox Check MX .

  • 0 Votes
    1 Posts

    I've had nodebb setup for a bit now and through some bumps and scrapes have always kept it running. After upgrading to V1.13.0 NodeBB would fail to load with a "Internal Server Error". After updating to 1.13.1 the website once again loads, however when trying to view any topics in the forums it times out loading. I've reviewed every possible plugin that could potentially be in the way and disabled several without success. I'm not seeing anything in the logs so may be looking in the wrong place. Everything is fully functional to posting new topics, viewing recent ones, discarding, deleting, purging, and the admin console. The only issue comes when its time to actually open a topic fully. The RSS Feeds properly display all the recent topics and content as well.

    My server is running MongoDB and proxied via nginx behind LetsEncrypt SSL Certificate, and can be seen at however does require a login, there is a single public post informing Guests that a login is required where you can see the issue.

    Any help on where to look for this and assistance in resolving would be appreciated.

  • 0 Votes
    3 Posts

    There are no error that show. Checked the log from the instance I ran for about 6 hours. It was the theme, though. I did the command given and it worked well. Thank you.

  • Admin timeout

    Solved Technical Support
    0 Votes
    2 Posts

    @Bruce-Lee don't think that's an option in ACP. It's in the code.