This sounds very similar to a problem that I reported a couple of weeks ago with imapd not closing the socket in 2.1.3. Maybe there is something not quite right with the socket handling in 2.x in general.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Gary Mills > Sent: Tuesday, 16 April 2002 10:05 a.m. > To: Lawrence Greenfield > Cc: [EMAIL PROTECTED] > Subject: Re: idle pop3d never times out > > > On Mon, Apr 15, 2002 at 02:40:20PM -0400, Lawrence Greenfield wrote: > > > > It appears that the client is still there (you have an active TCP > > session) but I don't know if it's making progress. Are the sequence > > numbers changing? > > No, they never change. I don't know much about TCP, but I'd say that > the client host is saying ``I'm full''. > > > It's almost as if someone Ctrl-z'd the pop client on their machine. > > > > Now, in terms on Cyrus: it's probably a bug (or at the very least a > > misfeature) that we don't implement any sort of timeout on write. > > This is mostly an implementation simplicity choice. > > I suppose it affects IMAP as well, but since IMAP allows multiple > sessions, the users don't notice. It looks as if I'll need to > add pop3d to my list of old processes that should be killed. > > -- > -Gary Mills- -Unix Support- -U of M Academic Computing and > Networking- > >
