On Tue, Jan 02, 2018 at 06:10:41PM +0000, Thorsten Glaser wrote: > David Bremner dixit: > > >The current state of nullmailer 2.x is that it requires systemd for > >support of the daemon functionality. > > > >Please see #884980, and #885537. Discussion of missing sysvinit support > >should go to the latter.
[reordered] > Even worse: my usual nullmailer use case is within a(n init-less) > chroot, so this is completely obliterating the *one* environment > in which one’d want to run it. Thorsten: just curious: how do you start and keep the queue runner running in an init- (and thus presunably rc-)less chroot? I only recently learned that nullmailer is much better than ssmtp as it can retry transient failures instead of immediately failing like ssmtp does, but in case you _can't_ or won't let it retry, you want ssmtp instead as it reports failure to the caller (in case it's a human trying to send them mail (reportbug, etc)), and saving it in a place that's more likely for a human to find. Thus: nullmailer is better if you have a functioning daemon-running harness, and ssmtp is better if you don't. > This is ridiculous. I guess I’ll just have to switch to sendmail > and accept Debian going even further down in niveau / functionality. > > Why, in three devils’ names, would a “simple” mail forwarder require > systemd out of a sudden? Amen to that. But, someone would have to fix the regression. Meow! -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable And Non-Discriminatory prices.
