I have been looking into this, and I have discovered that this behaviour
does not occur when using Exim 3.13. I was using Exim 3.22 when I
experienced these errors, and they seem to occur when mail was routed via
smtp. What is also strange is that sometimes the messages are logged and
sometimes they are not.
I am using the same config file for both versions. The only other difference
would be that for 3.13 I was using the Exim RPM's and for 3.22 I compiled
myself.
Paul
-----Original Message-----
From: Philip Hazel [
mailto:ph10@cus.cam.ac.uk]
Sent: 16 February 2001 09:16
To: Paul Wickham
Cc: 'exim-users@???'
Subject: Re: [Exim] Logging of messages piped to exim using -bS option
On Wed, 14 Feb 2001, Paul Wickham wrote:
> We are using exim for bsmtp but when a message is piped in using -bS
option
> the logs don't show an incoming message. Why is this or is there a tweak I
> can add to show th e incoming message?
This does not happen when I test. Exim should log *all* message
arrivals, by whatever means they come. So, the question is, what are you
doing that is special? Have you remembered to make the exim binary
setuid root? Have you tried running
exim -d9 -bS
....
to see if the debugging information gives you any clue as to what is
happening?
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
