Closed
Bug 336233
Opened 18 years ago
Closed 18 years ago
Mail message window "lags" behind one message
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 323752
People
(Reporter: aki, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2 Build Identifier: Thunderbird 1.5.0.2 When I open Thunderbird Inbox and select first message, nothing is shown in the preview pane or a separate message window. When I select next message, the previous message is shown. Some internal data strcture seems messed up, because Thunderbird remembers what message it had shown in place of the message that was selected. The other end is the Dovecot IMAP server, it seemed to me that Dovecot responded correctly (using Ethereal, although my knowledge of IMAP is somewhat limited). Reproducible: Always Steps to Reproduce: 1. Install Thunderbird and setup IMAP account 2. Start Thunderbird 3. Select a message in Inbox 4. Select another message in Inbox Actual Results: After selecting first message, preview window is blank. After selecting second message, contents of the first message is shown. Expected Results: After selecting first message, contents of the first message is shown in the preview window. After selecting second message contents of the second message is shown. Everything works fine with Thunderbird 1.0.x. Squirrelmail works just fine too. The other end is the Dovecot IMAP server http://www.dovecot.org/. Problem can be repeated with a clean installation of Thunderbird 1.5.0.2.
Comment 1•18 years ago
|
||
what version of the dovecot server? I believe they've fixed this on their end, though I'm not 100% sure if they've fixed a bug in their server, or worked around a bug in TB
Comment 2•18 years ago
|
||
Seems like a dupe of bug 323752 (where dovecot 1.0-stable is used). *** This bug has been marked as a duplicate of 323752 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•