Your message dated Wed, 17 Jul 2019 13:45:08 -0300 with message-id <87ims0vcdn....@tethera.net> and subject line Re: Bug#932123: nullmailer-send does not work as /var/spool/nullmailer/trigger is missing has caused the Debian Bug report #932123, regarding nullmailer-send does not work as /var/spool/nullmailer/trigger is missing to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 932123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: nullmailer Version: 1:2.2-3 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, The systemd unit file /lib/systemd/system/nullmailer.service does not create the fifo file /var/spool/nullmailer/trigger as their init.d equivalent did. That causes nullmailer-send to exit with the following error without sending the mail in the queue: Could not open trigger file: No such file or directory This could be solved adding to the systemd service definition (/lib/systemd/system/nullmailer.service) this line: ExecStartPre=-/usr/bin/mkfifo /var/spool/nullmailer/trigger ; /bin/chmod 0622 /var/spool/nullmailer/trigger Please find attached the patch file. Regards, Alejandro *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nullmailer depends on: ii debconf [debconf-2.0] 1.5.71 ii libc6 2.28-10 ii libgnutls30 3.6.7-4 ii libstdc++6 8.3.0-6 ii lsb-base 10.2019051400 nullmailer recommends no packages. nullmailer suggests no packages. -- debconf information: * nullmailer/adminaddr: asua...@teconecta.es nullmailer/defaultdomain: teconecta.es * nullmailer/relayhost: * shared/mailname: server-2.teconecta.es--- /lib/systemd/system/nullmailer.service 2019-07-15 14:53:14.744380161 +0200 +++ /lib/systemd/system/nullmailer.service.new 2019-07-15 15:06:27.609081283 +0200 @@ -7,6 +7,7 @@ [Service] WorkingDirectory=/var/spool/nullmailer +ExecStartPre=-/usr/bin/mkfifo /var/spool/nullmailer/trigger ; /bin/chmod 0622 /var/spool/nullmailer/trigger ExecStart=/usr/sbin/nullmailer-send User=mail Group=mail
--- End Message ---
--- Begin Message ---"Alejandro S." <alejandro...@gmail.com> writes: > I didn't noticed that files were being handled by systemd-tmpfiles. When > running the command above I discovered a problem with /var owner that made > fail systemd-tmpfiles. Once I'd solved that the trigger file was created > running 'dpkg-reconfigure nullmailer' and everything is running ok now. > > I'm sorry as it was only a permission problem in my machine. In the first > moment I'd think the creation of the trigger file was not handled at all, > but it is, so we can close this bug now. > > Thank you for the help. No problem, thanks for making a bug report with a patch. I think we should probably remove the redirection that hid the error in postinst, so probably some improvement will result. cheers, d
--- End Message ---
