[Exim] rcpt to takes up to 90 seconds

Top Page
Delete this message
Reply to this message
Author: Eddie McCreary
Date:  
To: 'exim-users@exim.org'
Subject: [Exim] rcpt to takes up to 90 seconds
I'm new to exim so I apologize if this is a common problem, however I
couldn't find anything in the
FAQ or the docs.

I need a simple exim setup for my home network, local delivery and
forwarding remote messages
onto the SMTP server of my ISP. I have it working, however it takes around
90 seconds for "rcpt to"
to validate the remote address and I can figure out why. I gather from the
docs that receiver_verify
is set to false by default, and running "exim -bP receiver_verify" I get
no_receiver_verify, so I assume
that's set properly.

Mail does go through, however I'd rather have exim just queue the message
and only have exim
validate the syntax of the address when my mail client connects.

I've appended the stderr from server with the debug level set to 11 and the
place where the pause
occurred marked. I'd appreciate any suggestions.

thanks,
Eddie

mercury:/etc/init.d# exim -bd -q30m -d11
Exim version 3.12 debug level 11 uid=0 gid=0
probably Berkeley DB version 1.8x (native mode)
mercury.home in local_domains? no (end of list)
Actual local interface address is 127.0.0.1
Actual local interface address is 192.168.1.4
Caller is an admin user
Caller is a trusted user
user name "root" extracted from gecos field "root"
port = 25
listening on all interfaces (IPv4)
pid written to /var/run/exim/exim.pid
LOG: 0 MAIN
exim 3.12 daemon started: pid=1060, -q30m, listening for SMTP on port 25
set_process_info: 1060 3.12 daemon: -q30m, listening on port 25
daemon running with uid=8 gid=8 euid=8 egid=8
SIGALRM received
1 queue-runner process running
Starting queue-runner: pid 1061
listening on port 25...
child 1061 ended: status=0x0
0 queue-runner processes now running
listening on port 25...
Connection request from 192.168.1.4
interface address = 192.168.1.4
host in rfc1413_hosts? yes (*)
sender_fullhost = [192.168.1.4]
sender_rcvhost = [192.168.1.4]
Process 1063 is handling incoming connection from [192.168.1.4]
host in host_lookup? yes (*)
looking up host name for 192.168.1.4
IP address lookup yielded mercury.home
Alias mercury
1 SMTP accept process running
listening on port 25...
Actual local interface address is 127.0.0.1
Actual local interface address is 192.168.1.4
local host found for non-MX address
mercury.home 192.168.1.4 -1
sender_fullhost = mercury.home [192.168.1.4]
sender_rcvhost = mercury.home ([192.168.1.4])
set_process_info: 1063 3.12 handling incoming connection from mercury.home
[192
.168.1.4]
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 mercury.home ESMTP Exim 3.12 #1 Mon, 30 Oct 2000 09:10:49 -0600
set_process_info: 1063 3.12 handling incoming connection from mercury.home
[192
.168.1.4]
ready for new message
smtp_setup_msg entered
SMTP<< helo mercury.home
sender_fullhost = mercury.home [192.168.1.4]
sender_rcvhost = mercury.home ([192.168.1.4])
set_process_info: 1063 3.12 handling incoming connection from mercury.home
[192
.168.1.4]
250 mercury.home Hello mercury.home [192.168.1.4]
SMTP<< mail from: <forge@mercury>
forge@mercury in sender_reject? no (option unset)
forge@mercury in sender_reject_recipients? no (option unset)
250 <forge@mercury> is syntactically correct
SMTP<< rcpt to: <beowulf@???>
heorot.org in local_domains? no (end of list)
heorot.org in relay_domains? no (end of list)

[the above is the last debug statement for almost 90 seconds]

local host found for non-MX address
localhost 127.0.0.1 -1
host in host_accept_relay? yes (192.168.1.0/16)
host is permitted to relay
sender is permitted to relay
250 <beowulf@???> is syntactically correct