Re: [EXIM] Strange Exim2.02 Problems with Error Messages

Top Page
Delete this message
Reply to this message
Author: Philip Hazel
Date:  
To: Lallek
CC: exim-users
Subject: Re: [EXIM] Strange Exim2.02 Problems with Error Messages
On Thu, 22 Oct 1998, Lallek wrote:

> Here is the logfile:
> -------snip-----------
> 1998-10-22 19:36:59 0zWLw1-000054-00 Process failed (69) when writing
> error message to bloedi@???
> ------snap-----------
>
> Here another...for the autoreply:
> ------snup-----------
> == looser@??? T=warning_t defer (0): Failed to send message from
> warning_t transport (69)
> ------snep-----------


An error is occurring when Exim tries to send itself the bounce message.
69 is EX_UNAVAILABLE which often means some program can't be found, but
Exim should be able to find itself. Does

exim -bP exim_path

give the correct path to the Exim binary? You could try delivering the
message with debugging turned on:

dexim -d9 -M 0zWLw1-000054-00

That might give a clue as to what is going wrong.


-- 
Philip Hazel            University of Cambridge Computing Service,
ph10@???      Cambridge, England. Phone: +44 1223 334714.



--
*** Exim information can be found at http://www.exim.org/ ***