Re: Exim delay at conection time
Felipe Alvarez Harnecker <felipe@qlsoft.cl> writes:
> Hi, having this problem i've tried this:
>
> exim -bh 192.168.1.60 -oMi 192.168.1.200
>
>
> **** SMTP testing session as if from host 192.168.1.60
> **** Not for real!
>
> >>> host in host_lookup? no (option unset)
> >>> host in host_reject? no (option unset)
> >>> host in host_reject_recipients? no (option unset)
> >>> host in auth_hosts? no (option unset)
> >>> host in sender_unqualified_hosts? no (option unset)
> >>> host in receiver_unqualified_hosts? no (option unset)
> >>> host in helo_verify? no (option unset)
> >>> host in helo_accept_junk_hosts? no (option unset)
> 220 dowjones.calalsa.cl ESMTP Exim 3.12 #1 Tue, 31 Oct 2000 13:04:18 -0300
>
>
> As you can see it seems that no lookup is made by exim, but when the
> real conection hapens from 192.168.1.60 ( and others ) i experience
> about 25 seconds of delay.
When 192.168.1.60 normally connects it will be coming in via. TCP to
the daemon, or possibly via. inetd. If it's being spawned by inetd
then TCP wrappers might be doing DNS lookups for you that are a
problem.
It's also possible that the daemon/inetd is badly loaded so that it
takes a lot of time to spawn the new exim (but I'd assume that you'd
have seen that).
My first guess is that it's a problem with whatever is connecting
from 192.168.1.60 (Ie. get them to try doing a simple telnet, and see
if that fails).
--
# James Antill -- james@and.org
:0:
* ^From: .*james@and.org
/dev/null
Reply to: