Tib, We had this problem when tcpserver was reverse mapping IP addresses. Maybe you need to disable reverse lookups? David Gartner Tib wrote: > So far as I have been able to find out by looking through the logs on the > system, the qmail-smtpd daemon stopped functioning around 19:30 on the > 24th of july. Nothing was changed on the system to instigate this, in fact > it was a static setup for the past 3 months or so. So on to the meat of > the matter: > > If you telnet to port 25 from localhost (unconfirmed just yet whether this > also works from immediate local network of 192.168.1 as well) qmail-smtpd > works great and responds in crisp order and delivers mail. However > anything outside of that in the real world guts of the internet will try > to connect to qmail-smtpd (which is spawned using tcpserver) will connect > and open a socket, but never receive the smtp banner. If you telnet to it > you will get as far as 'trying x.x.x.x - escape character is ^]' and > that's it. Outgoing mail is unhindered and local deliveries are also > perfectly functional. > > I used strace to dig through this a bit and found that when connected from > locally, communication was accepted both ways perfectly. However when > connecting from the external net, the communication happens up until > qmail-smtpd sends the banner text (which strace records as being sent), > but the banner text never gets to the other side (220 domain.tld ESMTP). > At that point all communication on that socket is dead - nothing transmits > and it eventually times out. With as much traffic as I get this can lead > up to about 40 open sockets with nothing going on. I've looked through the > HTML archives but could not find the problem so far. Anyone know what's > going on? > > <EOL> > Tib
