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

[Andreas Metzler]

Control: forwarded -1 https://bugs.exim.org/show_bug.cgi?id=2243

On 2018-02-12 Paul Slootman <paul at debian.org> wrote:
> On Mon 12 Feb 2018, Andreas Metzler wrote:
>> On 2018-02-12 Paul Slootman <paul at debian.org> wrote:
[...]
>>> 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 args: /usr/sbin/exim4 -bV

>>> I do have "arguments" included in my log_selector, I find it useful to


>> I am unable to verify that exim's behavior has changed from 4.89-2 to
>> 4.90.1-1 in this respect:
>> ametzler at argenau:/tmp/EXIM4$ exim4-daemon-light_4.89-1_amd64/usr/sbin/exim4 -bV > /dev/null
>> 2018-02-12 19:02:03 cwd=/tmp/EXIM4 2 args: exim4-daemon-light_4.89-1_amd64/usr/sbin/exim4 -bV
>> ametzler at argenau:/tmp/EXIM4$ exim4-daemon-light_4.90.1-1_amd64/usr/sbin/exim4 -bV > /dev/null
>> 2018-02-12 19:02:17 cwd=/tmp/EXIM4 2 args: exim4-daemon-light_4.90.1-1_amd64/usr/sbin/exim4 -bV

> Hmm, I was upgrading a bunch of systems yesterday, it could be that the
> system with the "arguments" in log_selector was another one, previously
> running 4.84.2-2+deb8u1.

Hello,

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.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'