Hi Mark,
Mark Delany wrote:
>
> On Thu, Jan 20, 2000 at 07:57:18AM +0800, Brian Baquiran wrote:
> > I did some checks last night. I telnetted to ports 25 and 110 on 192.168.0.2 and
> > discovered that it was taking a minute and a half for the smtp or POP3 servers
> > to issue a greeting. By then, most MUAs will have given up.
> >
> > When I checked early this morning, it was working fine again on both the live IP
> > and 192.168.0.1. I had not changed any settings.
>
> Did you check from the same IP address each time?
Both times, I checked from the mail server itself, from another server on the
192.168.0.x network, and from another server to poke at the live IP address.
> What output did you capture from tcpserver that leads you to believe that it
> may be a tcpserver problem?
Well, it's affected both qmail's SMTP and POP3. I figured if it were qmail, it
would affect only qmail-smtpd, as I understand the pop3 part is independent of
the rest. Also, the TCP connection is established (not refused), so I'm guessing
that tcpserver accepted the connection, but didn't run qmail-smtpd right away.
> > Is this a tcpserver problem (I can use inetd) or a qmail problem? This seems to
> > be the second tim e it has happened to this installation.
>
> There's a third possibility that it's an administrator/setup problem.
That's certainly a possibility. It's my first qmail installation. Strange thing
is, it has been working OK for the past couple of weeks.
> Which of the follow options are you using with tcpserver?
> -h, -H, -r, -R and -t and why?
I'm currently using -H (Do not look up the remote host name). I put it there the
last time we had this problem because we were having DNS problems at the same
time, and I thought not having to do a DNS lookup might help (it didn't). I
didn't remove it when the DNS problems went away and everything was working
again.
Thanks,
Brian
--
[EMAIL PROTECTED]
http://www.baquiran.com
US Fax: (603) 908-0727
AIM: bbaquiran
