smtp transport process returned non-zero status 0x0100: exit code 1

[William Craven]

I have recently upgraded our main mail server from Exim 3.03 to Exim
4.10 (yep I know - its a big jump) - and so far so good - it is working
very well. However, I have received every now and again the following
message as mailmaster...

Message 17kQQJ-0005P1-00 has been frozen.
non-zero status 0x0100: exit code 1

I am not sure what this is telling me - the appropriate msglog file
says...

2002-08-29 07:42:27 SMTP timeout while connected to
mtsbp024.naviantnetwork.net
[64.251.21.24] after initial connection: Connection timed out
2002-08-29 07:42:27 opt-***@mtsbp024.naviantnetwork.net R=dns T=smtp
defer (145):
Connection timed out: SMTP timeout while connected to
mtsbp024.naviantnetwork.n
et [64.251.21.24] after initial connection
2002-08-29 08:34:26 opt-***@mtsbp024.naviantnetwork.net R=dns T=smtp
defer (-1):
smtp transport process returned non-zero status 0x0100: exit code 1
*** Frozen

However, when I force delivery of the message it establishes connection
and delivers.

I am at a lost as to what this message is telling - any idea from the
group?

I am running this Exim server on a SunEnterprise E450 operating Solaris
7.

Thanks

Wm.
--
William Craven
ITServices Email: ***@ubc.ca
University of British Columbia Tel: [phone]
Vancouver, BC, Canada V6T 1Z2 Fax: [phone]

--

## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##

[Philip Hazel]

Post by William Craven

non-zero status 0x0100: exit code 1

I am not sure what this is telling me - the appropriate msglog file
says...

I'm not sure either. There is no code in Exim that returns a value of 1
from a transport process. If it had crashed, it should have given a
different return value.

Post by William Craven
2002-08-29 07:42:27 SMTP timeout while connected to
mtsbp024.naviantnetwork.net
[64.251.21.24] after initial connection: Connection timed out
Connection timed out: SMTP timeout while connected to
mtsbp024.naviantnetwork.n
et [64.251.21.24] after initial connection
smtp transport process returned non-zero status 0x0100: exit code 1
*** Frozen

The first failure happened at 07:42:27. I'm surprised not to see a "=="
log line for the message following those entries. Was there one?

The surprising entry happened at 08:34:26, which I assume was a
different delivery attempt. What is your configuration? Is is pretty
standard?

Post by William Craven
However, when I force delivery of the message it establishes connection
and delivers.

At the moment, I get a timeout when trying to connect to 64.251.21.24.

Are you seeing lots of these? Does a forced delivery always work?


--
Philip Hazel University of Cambridge Computing Service,
***@cus.cam.ac.uk Cambridge, England. Phone: [phone].


--

## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##