[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    [Bug 128233] IMAP protocol client error: fetching UID 0 causes lockup
From:       Andreas Aardal Hanssen <ahanssen () trolltech ! com>
Date:       2006-05-29 12:56:26
Message-ID: 20060529125626.31173.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=128233         




------- Additional Comments From ahanssen trolltech com  2006-05-29 14:56 -------
On Monday 29 May 2006 14:43, Carsten Burghardt wrote:
[bugs.kde.org quoted mail]

Perhaps, but the comma is perfectly fine. That simply means that the
client requested message 0 and 2005. But 0 is invalid. So maybe this
is several bugs ;-).

> > Bug 2: It shouldn't have done the full refresh in the first place. :-)
> Good catch!
> I wonder how you reproduce this behaviour. The 2006 was the highest UID so
> you must have deleted this messages before. Is that correct?


Indeed. It's very hard to reproduce; I'm running KMail against Binc IMAP
v1.2.13b2. It happens so seldomly that I've set up a protocol log
constantly at work to catch it when it happens. It does seem to happen
right after I delete a message, and after KMail refreshes its flags.

Andreas
_______________________________________________
KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel
[prev in list] [next in list] [prev in thread] [next in thread]