On Tue, 7 Sep 2004, Franz Georg [utf-8] Köhler wrote:
> 2004-09-07 19:36:58 1C4c5k-00035w-Rw == tanja.hofele@???
> <Tanja.Hofele@???> R=dnslookup T=remote_smtp defer (-1): smtp
> transport process returned non-zero status 0x000b: terminated by
> signal 11
>
> What would cause this?
Some kind of crash in the transport or something called by the
transport.
> A debugging run:
>
> hermes:/var/log# exim -d+all -M 1C4c5k-00035w-Rw
> 19:36:56 26512 Exim version 4.34 uid=0 gid=0 pid=26512 D=ffffffff
The latest release is 4.42. Have you tried that?
> 19:36:58 26513 tls_do_write(81196f8, 209)
> 19:36:58 26513 gnutls_record_send(SSL, 81196f8, 209)
> 19:36:58 26513 outbytes=209
> 19:36:58 26513 Calling gnutls_record_recv(8139230, bfffcfd0, 4096)
> 19:36:58 26512 reading pipe for subprocess 26513 (not ended)
> 19:36:58 26512 read() yielded 0
> 19:36:58 26512 remote delivery process 26513 ended: status=000b
That suggests it may be a crash inside GnuTLS. Perhaps it is this bug
that was fixed in 4.40:
18. If a server dropped the connection unexpectedly when an Exim client was
using GnuTLS and trying to read a response, the client delivery process
crashed while trying to generate an error log message.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
