Re: [EXIM] Problems with sending mail

Top Page
Delete this message
Reply to this message
Author: Philip Hazel
Date:  
To: Nolan Darilek
CC: exim-users
Subject: Re: [EXIM] Problems with sending mail
On Fri, 26 Dec 1997, Nolan Darilek wrote:

> mail for me. Local mail is handled perfectly. However, for remote
> messages, Exim reports that it can never connect to deliver the messages,
> or that the connection is refused. The resulting message is thus frozen,
> and undelivered. What frustrates me is, the logs seem to indicate that
> Exim has located the host, even listing its IP. However, none of the three
> messages which I had sent were delivered, thus I am led to believe that
> the problem lies at my end. An excerpt of the logs follows. Note that one
> email address is x'd out; I used the address for testing purposes and told
> the person that I would not distribute the address. Anyhow, logs follow:
> 1997-12-26 21:29:13 0xj3iA-0000DS-00 Message is frozen
> 1997-12-26 21:29:13 End queue run: pid=9919
> 1997-12-26 21:59:13 Start queue run: pid=9950
> 1997-12-26 22:00:30 0xlkz7-0001ZA-00 minor.opensound.com [193.94.53.107]: Connection refused
> 1997-12-26 22:01:46 0xlkz7-0001ZA-00 mail.eunet.fi [192.26.119.7]: Connection refused
> 1997-12-26 22:01:46 0xlkz7-0001ZA-00 == hannu@??? T=smtp defer (111): Connection refused
> 1997-12-26 22:01:46 0xlkGp-0001Tl-00 == xxxxxxx@??? T=smtp
> defer (-31): retry time not reached for any host
> 1997-12-26 22:01:49 0xljxO-0001Sh-00 == ndarilek@??? T=smtp defer (-31): retry time not reached for any host
> 1997-12-26 22:01:49 0xj3iA-0000DS-00 Message is frozen
> 1997-12-26 22:01:49 End queue run: pid=9950


The "Message is frozen" entry refers to message 0xj3iA-0000DS-00, which
isn't otherwise shown on that extract, so there is no evidence as to why
it was frozen.

"Connection refused" errors are relatively common when systems are being
rebooted.

I presume the xxxx's were a real domain that you want to keep hidden.

None of this looks exceptional. Are you still having problems? If so,
try running a delivery with debugging output turned on. For example, run

exim -d9 -M 0xljxO-0001Sh-00

The output will give a lot of information that might help in determining
what is going on.

-- 
Philip Hazel                   University Computing Service,
ph10@???             New Museums Site, Cambridge CB2 3QG,
P.Hazel@???          England.  Phone: +44 1223 334714



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