After more testing, I'm not sure it has anything to do with webmail, except that webmail calls for successive connections to imap.
I connected to binc multiple times in a row "telnet localhost imap" and then "^] quit" repeat... not too fast, much slower than xinetd's cut off for too fast connections. So it shouldn't be penalizing me, especially since I turned it way up. At any rate, it starts to hang, for 10 seconds, then a full 20. This is after I upgraded xinetd to the latest version 2.3.13 I believe. So, I guess the next step is to try tcpserver instead? I'm really at a loss as to what is causing this delay, the server has very little load, and memory usage is low. I don't need to actually do anything to binc to make the lag happen, just connecting seems to be enough, and not very fast either, maybe 10 times with a few seconds delay. It's definitely not a network problem, I'm ssh'ed into the box while connecting to localhost, there's not any lag on the ssh connection... hrmm, I just can't imagine what it could be... well on to tcpserver I guess. =) I'll let you know if that corrects the problem, I kind of doubt xinetd has this horrible problem that no one has noticed though, so it seems like this would be unrelated to xinetd or bincimap, but I can't think of what the third variable could be... =) Thanks, ben On 3:56:01 pm 02/16/05 Peter Stuge <[EMAIL PROTECTED]> wrote: > On Wed, Feb 16, 2005 at 01:29:34PM -0500, [EMAIL PROTECTED] wrote: > > Anyone have any sort of clue what might be causing this? I'm > > really at a loss. > > Sounds bad. Please check that the problem isn't with xinetd, one way > is to use tcpserver instead, I'm not sure how easy it is to debug > xinetd. > > Also, you can probably gather more information by following > http://lifewithbincimap.org/index.php/Main/ProtocolDumping > to debug the IMAP communication. > > > //Peter >
