Hi, This was reported a couple of days ago too on this list.
On further investigation, it looks like we already have a patch for this, but it never made it in (the contributor didn't mail it to evolution-patches). Sigh. See bug 42573. Michael On Thu, 2003-07-17 at 08:36, Thomas F. O'Connell wrote: > This line (from verbose output) seems consistently to precede the extended > hangs I'm getting: > > sending : A00726 UID FETCH 13475:* (FLAGS RFC822.SIZE INTERNALDATE > BODY.PEEK[HEADER.FIELDS.NOT (RECEIVED)]) > > Once that message is displayed, there is no more output until the hang > expires. > > I actually waited long enough to let Evolution time out, though, and these > are the error messages I get (in three separate dialogs): > > Error while 'Pinging IMAP server hostname': > Unexpected response from IMAP server: From: BAD Protocol Error: "Unknown command > found". > > Error while performing operation: > Unexpected response from IMAP server: Subject: BAD Protocol Error: "Unidentifiable > command specified". > However, the message was successfully sent. > > Error while 'Storing folder 'INBOX'': > Broken pipe _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
