On Thu, 14 Jun 2001, Oliver Cook wrote:
> I am loath to ignore this error, but I don't see what other choice
> I have with the information at my disposal.
Quite.
> Is is worth putting some more debugging into the code someplace, Philip,
> in case it happens again?
Well, I don't know what to do! Exim started its subprocess to send the
message, and the process yielded a return code of 1. It tells you that.
The calling Exim doesn't know much more...
Hmm. I suppose perhaps it should be doing something with the stdout
and/or stderr of the process. Actually, I think they are just the stdout
and stderr of the calling process - which won't go anywhere useful, I
suspect.
I'll put this one (getting more info) on a list to investigate in due
course, probably in the context of Exim 4.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
