On Mon, 10 Mar 2003, Van Howell wrote:
> 2003-03-10 10:39:16 18sPoU-0001ar-00 Unfrozen by forced delivery
> 2003-03-10 10:45:58 18sPoU-0001ar-00 == tinarcrouch@???
> <TinaRCrouch@???> R=dnslookup T=remote_smtp defer (-18): Remote host
> mailin-03.mx.aol.com [64.12.137.152] closed connection in response to
> initial connection
Well, that seems clear enough. Exim connected to 64.12.137.152 and the
connection was immediately closed by that host. At the moment, I can
connect without problem to that IP address. So I assume they had a
problem which has now been fixed. My hosts here have been delivering to
that address fine over the last couple of days, though I have logged
these errors:
2003-03-10 00:16:29 18sAxx-0002iT-00 mailin-04.mx.aol.com [64.12.137.152]: Connection reset by peer
2003-03-10 03:15:45 18sDlR-0003QT-00 mailin-03.mx.aol.com [64.12.137.152]: Connection reset by peer
From a couple of hours later, however, there have been no problems.
> here is some of the debug info (this is all I was able to capture if you
> need more I'll try again.)
For the future: the debug info is written to stderr. You can capture it
to a file in the usual way:
exim -d -M ..... 2>/some/file
Your debugging information just shows "reset by peer" and other "normal"
errors by the other end. It doesn't seem to have reproduced your
original problem:
> > 2003-03-04 16:48:29 18qLD3-0003EJ-00 == jamesvhowell@???
> > R=dnslookup T=remote_smtp defer (-1): smtp transport process returned
> > non-zero status 0x000b: terminated by signal 11
> > 2003-03-04 16:48:29 18qLD3-0003EJ-00 Frozen
So we are no nearer to figuring out what caused that. And I note that it
was a yahoo.com address that caused the original problem, whereas the
address above is an aol.com one.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
