On Thursday, April 2, 2020 6:18 PM, Grant Edwards <grant.b.edwa...@gmail.com> wrote:
> Nullmailer is also a good option with the added bonus of queueing > outbound mail while you're offline.: nullmailer is now configured, and test with `echo "Subject: ..." | sendmail -v m...@dom.com` works. but, smartd's test mail is not working, with this error: Apr 03 10:15:09 blah smartd[219171]: Test of <mail> to m...@dom.com produced unexpected output (65 bytes) to STDOUT/STDERR: Apr 03 10:15:09 blah smartd[219171]: mail: cannot send message: Process exited with a non-zero status Apr 03 10:15:09 blah smartd[219171]: Test of <mail> to m...@dom.com: failed (32-bit/8-bit exit status: 9216/36) tried to test `mail` in isolation: echo "test body" | mail -s "test subj" m...@dom.com --debug-level=3 mail: sendmail binary: /usr/sbin/sendmail mail: source=system, name=me, passwd=x, uid=1000, gid=1000, gecos=, dir=/home/me, shell=/bin/fish, mailbox=.maildir, quota=0, change_uid=1 mail: source=system, name=me, passwd=x, uid=1000, gid=1000, gecos=, dir=/home/me, shell=/bin/fish, mailbox=.maildir, quota=0, change_uid=1 mail: mu_mailer_send_message(): using From: me@localhost mail: Sending headers... mail: Sending body... mail: /usr/sbin/sendmail exited with: 1 mail: progmailer error: Process exited with a non-zero status mail: cannot send message: Process exited with a non-zero status mail: source=system, name=me, passwd=x, uid=1000, gid=1000, gecos=, dir=/home/me, shell=/bin/fish, mailbox=.maildir, quota=0, change_uid=1 i've also monitored `watch -n .1 tree /var/spool/nullmailer/` and verified that the queue never gets filled with any message when i use the `mail` command (which, i think, is what `smartd` uses). but, the queues get filled when i used `sendmail` by the command in my 1st paragraph. <side note about nullmailer> i like the queue functionality, so it is definitely more suitable for me than ssmtp. but i'm disappointed that it requires the service nullmailer to be running all the time. it should -imo- run in a triggered way upon calling sendmail, and should run once at bootup just to check if queue is not empty. and, if it runs, and is unable to empty the queue (e.g. due to no network availability) then it shall remain running until the network is back and the queue is empty. but, currently, it seems that the null mailer is just always running. disappoint! </side note about nullmailer>