On Fri, 4 Jul 2003, redmyrlin wrote:
> I think what has happened here is that previously the receiving smtp
> server didn't advertise TLS
> capability, so my server connected without SSL. Now, on the new server,
> it does advertise TLS
> capability so my server tries to initiate an SSL link which fails
> because I have not set up my OpenSSL correctly.
As long as Exim is compiled with TLS support (i.e. to use OpenSSL), it
should be able to function as a TLS client without any special
configuration.
> Has anyone else come across this behaviour? And what exactly is signal 11?
Signal 11 is "segmentation fault" - in other words a crash caused by an
attempt to address non-existent memory. Exim shouldn't do this - but it
is possible that the crash is inside OpenSSL, not in Exim itself. This
could be an direct OpenSSL problem, or an indirect problem in which the
way Exim calls OpenSSL provokes the problem.
Exim debugging output (add -d+tls to an exim command to run a delivery)
might give some clue as to exactly where the crash happens.
--
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
