Package: nullmailer
Version: 1:2.2-3
I use FAI to install debian 10 machines, and some of them uses
nullmailer to ship mail to a central smarthost.
The generated postinst script in nullmailer has a section like:
# Automatically added by dh_installinit/12
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" =
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
# In case this system is running systemd, we need to ensure that all
# necessary tmpfiles (if any) are created before starting.
if [ -d /run/systemd/system ] ; then
systemd-tmpfiles --create nullmailer.conf >/dev/null || true
fi
fi
# End automatically added section
The problem with this is that fai doesn't use systemd during the
install, but it's used when the machine reboots into the new install.
That causes the /var/spool/nullmailer/trigger pipe to never be created
and nullmailer doesn't work.
The sysvinit script shipped with nullmailer creates the pipe if it
doesn't exist, and the nullmailer systemd service should do something
equivalent.
//Anton
