Imapd after session opens almost immediately closes session and gives clients message the session has been closed. Here is some of the log entry from the server from the same time: (IP's and hostnames replace with X's) Mar 10 23:46:40 enterprise imapd[13780]: imap service init from XXX.XXX.XXX.XX Mar 10 23:46:40 enterprise imapd[13779]: Login user=robin host=X [XXX.XXX.XXX.XX] Mar 10 23:46:40 enterprise imapd[13780]: Login user=robin host=X [XXX.XXX.XXX.XX] Mar 10 23:46:42 enterprise imapd[13779]: Connection reset by peer, while reading line user=robin host=X [XXX.XXX.XXX.XX] Mar 10 23:46:42 enterprise imapd[13781]: imap service init from X Mar 10 23:46:42 enterprise imapd[13781]: Login user=robin host=X [XXX.XXX.XXX.XX] Mar 10 23:46:42 enterprise imapd[13780]: Killed (lost mailbox lock) user=robin host=X [XXX.XXX.XXX.XX] Mar 10 23:46:42 enterprise imapd[13780]: Logout user=robin host=X [XXX.XXX.XXX.XX] Mar 10 23:46:45 enterprise imapd[13781]: Connection reset by peer, while reading line user=robin host=X [XXX.XXX.XXX.XX] Note: For a temporary fix I downgraded back to the IMAP-4.5 package.
That seems like the result of non-standard behaviour by the client, and probably not the server. I'll log an entire transsaction between outlook and imapd and see what exactly causes the trouble, it shouldn't be too difficult. -Stan Bubrouski
assigned to the new owner
Is the user attempting to access the mailbox on the server or with a second IMAP connection concurrent to the one which shuts down?
Is this still an open issue or can we close it?
Closing bug, lack of feedback, can't reproduce. Considering the number of people using Outlook, if this was a real bug, I'd suspect the incoming reports to be much higher. Running OutBreak Express I've been unable to reproduce it in latest errata releases.
*** Bug 10950 has been marked as a duplicate of this bug. ***