MailGun Not Working NodeBB

Solved Configure
  • Hi
    I setted mail server as mailgun.
    But forum not sending registered email .

  • @cagatay said in MailGun Not Working NodeBB:

    Hi
    I setted mail server as mailgun.
    But forum not sending registered email .

    022-11-04T13:07:20.734Z [4568/172189] - error: [user.create] Validation email failed to send
    [emailer.send] Error: Invalid login: 535 Authentication failed
        at SMTPConnection._formatError (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:784:19)
        at SMTPConnection._actionAUTHComplete (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:1536:34)
        at SMTPConnection.<anonymous> (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:540:26)
        at SMTPConnection._processResponse (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:947:20)
        at SMTPConnection._onData (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:749:14)
        at TLSSocket.SMTPConnection._onSocketData (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:189:44)
        at TLSSocket.emit (events.js:400:28)
        at addChunk (internal/streams/readable.js:293:12)
        at readableAddChunk (internal/streams/readable.js:267:9)
        at TLSSocket.Readable.push (internal/streams/readable.js:206:10)
    2022-11-04T13:08:50.302Z [4568/172189] - error: [user.create] Validation email failed to send
    [emailer.send] Error: Invalid login: 535 Authentication failed
        at SMTPConnection._formatError (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:784:19)
        at SMTPConnection._actionAUTHComplete (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:1536:34)
        at SMTPConnection.<anonymous> (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:540:26)
        at SMTPConnection._processResponse (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:947:20)
        at SMTPConnection._onData (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:749:14)
        at TLSSocket.SMTPConnection._onSocketData (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:189:44)
        at TLSSocket.emit (events.js:400:28)
        at addChunk (internal/streams/readable.js:293:12)
        at readableAddChunk (internal/streams/readable.js:267:9)
        at TLSSocket.Readable.push (internal/streams/readable.js:206:10)
    2022-11-04T13:08:50.302Z [4568/172189] - error: admin.user.sendValidationEmail
    Error: Email sending failed for the following uids, check server logs for more info: 5
        at User.sendValidationEmail (/home/nojor/nodebb/src/socket.io/admin/user.js:91:9)
        at runMicrotasks (<anonymous>)
        at processTicksAndRejections (internal/process/task_queues.js:95:5)
        at async onMessage (/home/nojor/nodebb/src/socket.io/index.js:160:19)
    2022-11-04T13:12:42.634Z [4568/172189] - error: [user.create] Validation email failed to send
    [emailer.send] Error: Invalid login: 535 Authentication failed
        at SMTPConnection._formatError (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:784:19)
        at SMTPConnection._actionAUTHComplete (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:1536:34)
        at SMTPConnection.<anonymous> (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:540:26)
        at SMTPConnection._processResponse (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:947:20)
        at SMTPConnection._onData (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:749:14)
        at TLSSocket.SMTPConnection._onSocketData (/home/nojor/nodebb/node_modules/nodemailer/lib/smtp-connection/index.js:189:44)
        at TLSSocket.emit (events.js:400:28)
        at addChunk (internal/streams/readable.js:293:12)
        at readableAddChunk (internal/streams/readable.js:267:9)
        at TLSSocket.Readable.push (internal/streams/readable.js:206:10)
    2022-11-04T13:12:42.634Z [4568/172189] - error: admin.user.sendValidationEmail
    Error: Email sending failed for the following uids, check server logs for more info: 5
        at User.sendValidationEmail (/home/nojor/nodebb/src/socket.io/admin/user.js:91:9)
        at runMicrotasks (<anonymous>)
        at processTicksAndRejections (internal/process/task_queues.js:95:5)
        at async onMessage (/home/nojor/nodebb/src/socket.io/index.js:160:19)
    
  • @cagatay said in MailGun Not Working NodeBB:

    Error: Invalid login: 535 Authentication failed

    The clue is in the error message

    Error: Invalid login: 535 Authentication failed
    

    You should check the username and password.

  • @phenomlab it should be created by mailgun or my mail is also working yandex.

    that user and pass yandex mail but service mailgun how can i fix it i do not know.

    320ad480-68f6-4dac-b48c-3623a1469f7e-image.png

  • @cagatay What happens if you try to send a test message?

  • @phenomlab did it 🙂 i did not create smtp user on mailgun. everything is working now.

    6cc6061f-ed5d-41f6-8eb7-5d98f98b3706-image.png

  • cagatayundefined cagatay has marked this topic as solved on

Did this solution help you?
Did you find the suggested solution useful? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation💗

  • Composer options on nodebb

    Solved Configure
    8
    3 Votes
    8 Posts
    79 Views

    @Panda You should be able to expose the CSS for these using F12 to get into console

    3591518c-e3a3-4ada-a43c-6b32a5e0359c-image.png

    a2b8ed46-4157-4ff2-85f0-576543380107-image.png

    That should then expose the element once selected

    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; }
  • 0 Votes
    2 Posts
    36 Views

    @mventures Quick reply is basically exactly that. However, it’s possible to trigger the full composer as below

    82ca1209-31be-4a51-a641-9887b5a238b8-image.png

    Failing that, you’ll need to use the reply button in the sticky toolbar

    1d230bcb-ff8e-4756-94f7-6e2fb7a94bc4-image.png

  • NodeBB: Consent page

    Solved Configure
    16
    4 Votes
    16 Posts
    217 Views

    @DownPW I still do not see any issues.

  • 1 Votes
    2 Posts
    62 Views

    @phenomlab

    In fact I specified the sub rep and not the rep

    DON’T DO THIS:

    nodebb@nodebbpwclonedb:~/nodebb$ sudo mongorestore --username admin --password XXXXXXXXXXXXXX --nsInclude nodebb.objects --drop /home/nodebb/nodebb_DB_20230107/nodebb/

    BUT THIS :

    nodebb@nodebbpwclonedb:~/nodebb$ sudo mongorestore --username admin --password XXXXXXXXXXXXXX --nsInclude nodebb.objects --drop /home/nodebb/nodebb_DB_20230107/

    🙂

  • 5 Votes
    13 Posts
    188 Views
    'use strict'; const winston = require('winston'); const user = require('../user'); const notifications = require('../notifications'); const sockets = require('../socket.io'); const plugins = require('../plugins'); const meta = require('../meta'); module.exports = function (Messaging) { Messaging.notifyQueue = {}; // Only used to notify a user of a new chat message, see Messaging.notifyUser Messaging.notifyUsersInRoom = async (fromUid, roomId, messageObj) => { let uids = await Messaging.getUidsInRoom(roomId, 0, -1); uids = await user.blocks.filterUids(fromUid, uids); let data = { roomId: roomId, fromUid: fromUid, message: messageObj, uids: uids, }; data = await plugins.hooks.fire('filter:messaging.notify', data); if (!data || !data.uids || !data.uids.length) { return; } uids = data.uids; uids.forEach((uid) => { data.self = parseInt(uid, 10) === parseInt(fromUid, 10) ? 1 : 0; Messaging.pushUnreadCount(uid); sockets.in(`uid_${uid}`).emit('event:chats.receive', data); }); if (messageObj.system) { return; } // Delayed notifications let queueObj = Messaging.notifyQueue[`${fromUid}:${roomId}`]; if (queueObj) { queueObj.message.content += `\n${messageObj.content}`; clearTimeout(queueObj.timeout); } else { queueObj = { message: messageObj, }; Messaging.notifyQueue[`${fromUid}:${roomId}`] = queueObj; } queueObj.timeout = setTimeout(async () => { try { await sendNotifications(fromUid, uids, roomId, queueObj.message); } catch (err) { winston.error(`[messaging/notifications] Unabled to send notification\n${err.stack}`); } }, meta.config.notificationSendDelay * 1000); }; async function sendNotifications(fromuid, uids, roomId, messageObj) { const isOnline = await user.isOnline(uids); uids = uids.filter((uid, index) => !isOnline[index] && parseInt(fromuid, 10) !== parseInt(uid, 10)); if (!uids.length) { return; } if (roomId != 11) { // 5 Is the ID of the ID of the global chat room. Messaging.getUidsInRoom(roomId, 0, -1); // Proceed as normal. } else { user.getUidsFromSet('users:online', 0, -1); // Only notify online users. } const { displayname } = messageObj.fromUser; const isGroupChat = await Messaging.isGroupChat(roomId); const notification = await notifications.create({ type: isGroupChat ? 'new-group-chat' : 'new-chat', subject: `[[email:notif.chat.subject, ${displayname}]]`, bodyShort: `[[notifications:new_message_from, ${displayname}]]`, bodyLong: messageObj.content, nid: `chat_${fromuid}_${roomId}`, from: fromuid, path: `/chats/${messageObj.roomId}`, }); delete Messaging.notifyQueue[`${fromuid}:${roomId}`]; notifications.push(notification, uids); } };
  • restarting nodebb on boot

    Unsolved Configure
    3
    1 Votes
    3 Posts
    81 Views

    @eeeee said in restarting nodebb on boot:

    can I just run nodebb under nodemon for auto restarts?

    It’s a better method. Nodemon just looks for file system changes and would effectively die if the server was rebooted meaning you’d have to start it again anyway. Systemd is the defacto standard which is how the operating system interacts in terms of services, scheduled tasks etc.

  • Configure SMTP for Nodebb

    Solved Configure
    14
    5 Votes
    14 Posts
    413 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.

  • NodeBB metadata

    Solved Configure
    4