Comment # 9 on bug 1206367 from
(In reply to Thorsten Kukuk from comment #8)

> - try MAILX_OPTIONS
> (https://manpages.opensuse.org/Tumbleweed/systemd-status-mail/systemd-status-
> mail.8.en.html)

Ah, a new option :-)

I have now a working mailx configuration, can send from command line.
With mailx-options......

> Your mail setup is not a problem of systemd-status-mail, this tool expects a
> working mail setup (like e.g. cron does, too) and is no replacement for it.

....I run into the next error:

an 10 11:45:48 localhost.localdomain systemd[1]: Starting Send status mail for
test.service...
Jan 10 11:45:48 localhost.localdomain systemd-status-mail[14744]: postdrop:
fatal: mail_queue_enter: create file maildrop/302666.14744: no permission
Jan 10 11:45:48 localhost.localdomain postfix/postdrop[14744]: fatal:
mail_queue_enter: create file maildrop/302666.14744: no permission
Jan 10 11:45:49 localhost.localdomain systemd-status-mail[14740]: sendmail:
warning: command "/usr/sbin/postdrop -r" exited with status 1
Jan 10 11:45:49 localhost.localdomain systemd-status-mail[14740]: sendmail:
fatal: root@localhost.localdomain(65534): unable to execute /usr/sbin/postdrop
-r: Application error
Jan 10 11:45:49 localhost.localdomain postfix/sendmail[14740]: warning: command
"/usr/sbin/postdrop -r" exited with status 1
Jan 10 11:45:49 localhost.localdomain postfix/sendmail[14740]: fatal:
root@localhost.localdomain(65534): unable to execute /usr/sbin/postdrop -r:
Application error
Jan 10 11:45:49 localhost.localdomain systemd[1]:
systemd-status-mail@test.service.service: Main process exited, code=exited,
status=1/FAILURE
Jan 10 11:45:49 localhost.localdomain systemd[1]:
systemd-status-mail@test.service.service: Failed with result 'exit-code'.
Jan 10 11:45:49 localhost.localdomain systemd[1]: Failed to start Send status
mail for test.service.

This is a MicroOS Desktop system.
Create a new bug?


You are receiving this mail because: