--On 21 July 2006 13:42:40 +0100 Ian Eiloart <iane@???> wrote:
>
> Thread 0 Crashed:
> 0 libcrypto.0.9.8.dylib 0x003c547c CRYPTO_add_lock + 108
> (icplusplus.c:28)
> 1 libcrypto.0.9.8.dylib 0x00445440 asn1_item_combine_free + 520
> (icplusplus.c:28)
> Binary Images Description:
> 0x1000 - 0xb0fff exim /opt/local/sbin/exim
> 0xd2000 - 0xdafff liblber-2.2.7.dylib
> /opt/local/lib/liblber-2.2.7.dylib 0x205000 - 0x2b3fff
> libdb-4.3.dylib /opt/local/lib/libdb-4.3.dylib 0x2cd000 -
> 0x2f3fff libldap-2.2.7.dylib /opt/local/lib/libldap-2.2.7.dylib
> 0x377000 - 0x3aefff libssl.0.9.8.dylib
> /opt/local/lib/libssl.0.9.8.dylib
> 0x3c4000 - 0x4b5fff libcrypto.0.9.8.dylib
> /opt/local/lib/libcrypto.0.9.8.dylib 0x520000 - 0x532fff
> libsasl2.2.dylib /opt/local/lib/libsasl2.2.dylib
OK, I've fixed this now. I was using DarwinPorts (with my own port
definition).
The problem was that DarwinPorts has openssl 0.9.8 - and this seems to
break exim with TLS.
When I link against the OSX inbuild openssl 0.9.7 instead, the exim seems
to work OK. That is, I get a "220 TLS go ahead" instead of a dropped
connection.
For the benefit of those who slated (off list) OSX as a server platform, my
exim logs and ktrace weren't of too much benefit - they got me so far, but
no further. The OSX crash log - which I've not seen the like of elsewhere -
gave me the clue that I needed to fix this problem.
--
Ian Eiloart
IT Services, University of Sussex
