Why Emails are not sending properly for new Registered users

Varun Ganesh D

Im using Amazon Ses
Previous version was perfect
After updating emails are not sending properly
Showing error logs like this

2020-11-09T05:58:29.322Z [4567/15105] - [31merror[39m: Error: spawn sendmail ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
    at onErrorNT (internal/child_process.js:469:16)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)
    at runNextTicks (internal/process/task_queues.js:66:3)
    at processImmediate (internal/timers.js:429:9)
2020-11-09T05:58:29.387Z [4567/15105] - [31merror[39m: Error: spawn sendmail ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
    at onErrorNT (internal/child_process.js:469:16)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)
    at runNextTicks (internal/process/task_queues.js:66:3)
    at processImmediate (internal/timers.js:429:9)
2020-11-09T05:58:29.455Z [4567/15105] - [31merror[39m: Error: spawn sendmail ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
    at onErrorNT (internal/child_process.js:469:16)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)
LOGS CONTROL PANEL

julian

@varun-ganesh-d spawn sendmail ENOENT means NodeBB is attempting to send emails by calling the local sendmail executable, which does not exist.

You'll need to re-check your amazon SES configuration settings... is this via plugin or direct via ACP?

Varun Ganesh D

@julian Direct ACP

PitaJ

@varun-ganesh-d please share your email settings. You may hide any sensitive information.

gotwf

@Varun-Ganesh-D After updating what? Do not know jack about SES but seems whacked to me that updating only NodeBB would result in such. Perchance might some other, more system wide updates also been in the lurking?

Presuming you have cli access, what returns when thou drivest the following:

[root@forums ~]# which sendmail
/usr/sbin/sendmail

Should be similar to above, and, of course, be in your $PATH.

Rock on!