Bug#890236: exim4-daemon-heavy: /usr/sbin/exim4 -bV with log_selector = arguments logs to stderr

2018-02-18 Thread Paul Slootman
On Sun 18 Feb 2018, Andreas Metzler wrote: > > I have rebuilt 4.84.2-2+deb8u1 on sid and did not see a different > behavior. However running exim in a jessie chroot shows the "old" > behavior you described. (stretch does not). So I think this might have > been caused by changes outside exim. I

Bug#890236: exim4-daemon-heavy: /usr/sbin/exim4 -bV with log_selector = arguments logs to stderr

2018-02-18 Thread Andreas Metzler
Control: forwarded -1 https://bugs.exim.org/show_bug.cgi?id=2243 On 2018-02-12 Paul Slootman wrote: > On Mon 12 Feb 2018, Andreas Metzler wrote: >> On 2018-02-12 Paul Slootman wrote: [...] >>> After upgrading from 4.89-2 to 4.90-1.1 I get a mail from the

Bug#890236: exim4-daemon-heavy: /usr/sbin/exim4 -bV with log_selector = arguments logs to stderr

2018-02-12 Thread Paul Slootman
On Mon 12 Feb 2018, Andreas Metzler wrote: > On 2018-02-12 Paul Slootman wrote: > > Package: exim4-daemon-heavy > > Version: 4.90.1-1 > > Severity: normal > > > After upgrading from 4.89-2 to 4.90-1.1 I get a mail from the cron.daily > > run, due to /usr/sbin/exim4 -bV

Bug#890236: exim4-daemon-heavy: /usr/sbin/exim4 -bV with log_selector = arguments logs to stderr

2018-02-12 Thread Andreas Metzler
On 2018-02-12 Paul Slootman wrote: > Package: exim4-daemon-heavy > Version: 4.90.1-1 > Severity: normal > After upgrading from 4.89-2 to 4.90-1.1 I get a mail from the cron.daily > run, due to /usr/sbin/exim4 -bV outputting this line to stderr instead > of to

Bug#890236: exim4-daemon-heavy: /usr/sbin/exim4 -bV with log_selector = arguments logs to stderr

2018-02-12 Thread Paul Slootman
Package: exim4-daemon-heavy Version: 4.90.1-1 Severity: normal After upgrading from 4.89-2 to 4.90-1.1 I get a mail from the cron.daily run, due to /usr/sbin/exim4 -bV outputting this line to stderr instead of to /var/log/exim4/mainlog like it used to: 2018-02-12 11:34:05.084 [29152] cwd=/tmp 2