I just tested it again and timed it. 10 seconds until I get the banner from the time I connect and issue the EHLO command. That's unacceptable, it should be nearly instant. It's not like this is a slow box or anything (dual xeon box, it's got some ummph).
Any ideas as to why the long delay? Also, you wanted me to run the command "ps auxwww |grep '[t]cpserver .*qmail-smtpd'": vpopmail 3628 0.0 0.1 2104 1328 ? S 07:48 0:00 /usr/local/bin/tcpserver -v -R -l rhost1.zfx.com -x /etc/tcp.smtp.cdb -c 50 -u 89 -g 89 0 smtp /var/qmail/bin/qmail-smtpd rhost1.zfx.com /var/vpopmail/bin/vchkpw /bin/true Thanks, Chris Miller Compuville www.compuville.net -----Original Message----- From: Peter Palmreuther [mailto:[EMAIL PROTECTED] Sent: Monday, April 26, 2004 2:55 PM To: Chris Miller in vpop Subject: [vchkpw] Re: SMTP Slowness Hello Chris, On Monday, April 26, 2004 at 3:42:40 PM you wrote (at least in part): > Now I've got another problem with SMTP. When I try to connect, it takes > FOREVER to send the welcome message. Go ahead and telnet into rhost1.zfx.com > on port 25 and issue a HELO, and you'll see what I mean. Both, connecting and issuing a EHLO (or HELO), is just a matter of seconds from here. > I thought that it could be something with DNS, but everything seems > fine with DNS. The hostname and reverse DNS entries for the box are > in there, and the DNS servers on the server are set correctly so it > should be able to resolve it's self pretty quickly (the DNS server > it uses is on the local box, as is the zone for the domain). Well, it nevertheless could be a DNS related problem. The "self referring" reverse entries are not that much of a matter. What takes time most times this behavior is seen is reverse resolving of connecting client. So what's your 'tcpserver ... qmail-smtpd' invocation line[1]? [1]: ps auxwww |grep '[t]cpserver .*qmail-smtpd' -- Best regards Peter Palmreuther Progress is made on alternate Fridays.
