Re: [Exim] tls problems in exim-4.30

Página Inicial
Delete this message
Reply to this message
Autor: T. Horsnell (tsh)
Data:  
Para: exim-users
CC: ph10
Assunto: Re: [Exim] tls problems in exim-4.30
>On Tue, 6 Apr 2004, T. Horsnell (tsh) wrote:
>
>> I have a curious problem with exim-4.30 on an Alpha
>> running Tru64 V5.1B. Apart from the build-error below
>> (which is fixed by adding the line:
>>
>> typedef int socklen_t;
>>
>> to exim.h)
>
>Hmm. The configuration for "OSF1" (what is now Tru64) contains
>
>#define SOCKLEN_T    size_t

>
>which is supposed to cope with this. Oh! you are talking about 4.30.
>This is fixed in 4.31.
>
>But 4.32 will be out fairly soon to fix some other things; you might as
>well wait at this stage.


OK, will do.


>
>> I also get a configfile error at startup. The program is built with
>> the appropriate TLS options enabled, but when it starts, it complains
>> about tls_option lines:
>>
>> # /local/src/exim/exim-4.30-TLS/build-OSF1-alpha/exim -bdf -q1h -C /local/src/exim/exim-4.30-TLS/configure
>> 2004-04-06 18:13:58 Exim configuration error in line 10 of /local/src/exim/exim-4.30-TLS/configure:
>> main option "tls_advertise_hosts" unknown
>>
>> and yet still offers STARTTLS at the SMTP EHLO command:
>
>That's impossible. A configuration error prevents Exim from starting up.
>I suspect an old version is still running.
>
>What does
>
>/local/src/exim/exim-4.30-TLS/build-OSF1-alpha/exim -bV
>
>say? It should list TLS if it supports it.
>


alf1_root> /local/src/exim/exim-4.30-TLS/build-OSF1-alpha/exim -bV -C /local/src/exim/exim-4.30-TLS/configure
Exim version 4.30 #3 built 07-Apr-2004 10:43:46
Copyright (c) University of Cambridge 2003
Probably ndbm
Support for: iconv() OpenSSL
Lookups: lsearch wildlsearch nwildlsearch dbm dmbnz
Authenticators: cram_md5 plaintext spa
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile autoreply pipe smtp
Fixed never_users: 0
Configuration file is /local/src/exim/exim-4.30-TLS/configure
alf1_root>


And it really does keep running after the configfile error.
I'm running it with the -bdf switches for testing. Would this
make any difference? I'm using port 26 for test, and without this
test version running a telnet to port 26 fails.

alf1_tsh> telnet alf1 26
Trying 10.1.0.1...
Connected to alf1.lmb.internal.
Escape character is '^]'.
220 alf1.lmb.internal ESMTP Exim 4.30 Wed, 07 Apr 2004 10:52:30 +0100
EHLO alf1
250-alf1.lmb.internal Hello alf1.lmb.internal [10.1.0.1]
250-SIZE 52428800
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP


There is a production version running on port 25, built without TLS
and using a different config file:

alf1_root> telnet alf1 25
Trying 10.1.0.1...
Connected to alf1.lmb.internal.
Escape character is '^]'.
220 alf1.lmb.internal ESMTP Exim 4.30 Wed, 07 Apr 2004 10:49:45 +0100
EHLO alf1
250-alf1.lmb.internal Hello alf1.lmb.internal [10.1.0.1]
250-SIZE 52428800
250-PIPELINING
250 HELP

Would the 'make' log help?

Cheers,
Terry

>
>--
>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

>