Philip,
No, I am not seeing anything in the logs.
Using your initial example:
bash-2.03# /usr/local/exim/bin/exim -be
> ${readsocket{/non/exist}{abcd}{5s}{\n}{socket-error}}
socket-error
> ${readsocket{/non/exist}{abcd}{5s}{\n}}
Failed: failed to connect to socket /non/exist: No such file or directory
>
it looks like if I provide an error expansion string {socket-error}, that
it doesn't generate the error. If I don't provide the error expansion
string (so that I'll get the error) how can I tell (in the code) if the
readsocket is failing?
Please respond to exim-users@???
To: Dan_Mitton@???
cc: exim-users@???
Subject: Re: [exim] readsocket
LSN: Not Relevant
User Filed as: Not a Record
On Thu, 18 Jan 2007, Dan_Mitton@??? wrote:
> Ok, if it leaves the error "failed to connect..." in a variable, then I
> can test that. What variable??
Sorry. I should have been more explicit. I meant a C variable, not an
Exim variable. But, as I said,
> Which ACL is this called from? Looking at the code, it should return an
> error indication from the attempt to run the ACL, and this should
> normally show the message.
You should see something on the log when an ACL fails because of a
failing expansion error. Do you not see anything?
--
Philip Hazel University of Cambridge Computing Service
Get the Exim 4 book: http://www.uit.co.uk/exim-book
