On Tue, Apr 17, 2001 at 07:44:23PM -0700, Michael Werneke wrote:
> Telnetting to port 110 is successful. Surely there must be a workaround for
> this. This setup has been working for months in the same configuration for
> months with the same mail clients. What could cause it to stop working over
> night?
What is your startup sequence for tcpserver?
If your/your clients DNS is broken "overnight" (some unnoticed syntax error in
zone file e.g.) this may exactly be the symptoms.
What exactly do you mean by "pop3 connections keep timing out" ?
If you do a
$ telnet pophost pop3
do you get a "prompt" like
+OK <[EMAIL PROTECTED]>
or is it hanging like
$ telnet popmail pop3
Trying 195.30.0.14...
Connected to popmail.Space.Net.
Escape character is '^]'.
[ hanging now ]
If it's the latter, you may add "-H", "-l <localname>" and remove (if
present) the "-p" flag to tcpserver.
Also, you may have reached a capacity limit. If you have really a *lot*
of clients connecting you may hit the default for simultaneous
connections (=40), but from the log you've posted I don;t think this is
the case (tcpserver: status: 2/40 - means 2 active connections out of
40 simultaneous allowed).
What puzzled me in your log is the line:
Apr 17 18:36:05 alpha pop3d: 987557765.215412 tcpserver: ok 2010
:111.222.77.121:110 adsl-11-222-33-87.dsl.sndg02.dslisp.net:11.222.33.87::3015
I can neither get records for
adsl-11-222-33-87.dsl.sndg02.dslisp.net (NXDOMAIN)
nor
87.33.222.11.in-addr.arpa (NXDOMAIN)
\Maex
--
SpaceNet AG | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development | D-80807 Muenchen | Fax: +49 (89) 32356-299
Stress is when you wake up screaming and you realize you haven't fallen
asleep yet.
