Have you found any solution, work around ?
I am having the same problem, with both imapd and pop3d
as you see they hang there since wednesday. the clients are outlook express.
42564 0.0 0.2 2392 316 p2- I Wed12AM 0:02.67
/usr/local/cyrus2/bin/master
cyrus 42821 0.0 0.4 3752 664 p2- I Wed01AM 0:03.32 imapd: imapd:
alchemistry.net[192.168.0.3] (imapd)
cyrus 70493 0.0 0.6 3820 996 ?? S Wed07PM 0:00.73 imapd: imapd:
sharkjr[192.168.0.22] eugene user.eugene (imapd)
cyrus 73125 0.0 0.4 3752 656 ?? I Wed09PM 0:00.53 imapd: imapd:
alchemistry.net[192.168.0.3] (imapd)
cyrus 73951 0.0 0.4 3752 596 ?? I Wed10PM 0:00.34 imapd: imapd:
alchemistry.net[192.168.0.3] (imapd)
n Mon, Apr 15, 2002 at 07:28:34PM -0500, Gary Mills wrote:
> On Tue, Apr 16, 2002 at 11:33:00AM +1200, Mike Brady wrote:
> > 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.
>
> No, it's not the same. In my case pop3d was in the middle of a write
> to the client. The client wasn't reading the data, causing the
> connection to persist forever.
>
> --
> -Gary Mills- -Unix Support- -U of M Academic Computing and Networking-
>
