Closed
Bug 689726
Opened 13 years ago
Closed 13 years ago
Message tags disappear when new email received
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 675868
People
(Reporter: mail, Unassigned)
Details
Observed in:
Thunderbird 6.0.2
Thunderbird 7.0
Observed on:
Microsoft Windows 7 (64-bit), Service Pack 1
Reproducible: intermittent; occurs several times a day throughout a typical inbox-drive work environment.
Steps to reproduce:
1. Apply one or more tags to one or more messages in an IMAP inbox.
2. Receive a new email message.
Expected result:
All tags remain as they were.
What is actually observed:
All tags disappear from all messages in the inbox.
Other actions tested, no bug observed, yet results inconclusive due to intermittent nature of bug:
- Composing and sending a new email
- Switching to a different folder and back to the inbox
- Restarting Thunderbird
Comment 1•13 years ago
|
||
Is your imap server a dovecot server, by chance? With lazywrite turned on?
Reporter | ||
Comment 2•13 years ago
|
||
(In reply to David :Bienvenu from comment #1)
> Is your imap server a dovecot server, by chance? With lazywrite turned on?
I don't know; if you can tell me how to determine that, I will check and let you know.
Comment 3•13 years ago
|
||
you can tell if it's a dovecot server by getting an imap protocol log and looking at the greeting returned by the server - https://wiki.mozilla.org/MailNews:Logging
re lazywrite, you'd need to ask your server admin, though if it is a dovecot server, I'm pretty sure you're seeing the lazywrite problem.
Reporter | ||
Comment 4•13 years ago
|
||
If I am reading this right, then yes, it is a dovecot server: "4028[a362340]: 91aa800:<domain>:NA:CreateNewLineFromSocket: * OK Dovecot ready."
Comment 5•13 years ago
|
||
You need to contact your sysadmin and let him know. See http://www.dovecot.org/list/dovecot/2009-March/037864.html for more info.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•