Closed Bug 541900 Opened 16 years ago Closed 16 years ago

Compacting folders causes many messages to be marked unread

Categories

(Thunderbird :: Folder and Message Lists, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 540554

People

(Reporter: mozilla06b, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.6) Gecko/20091216 Fedora/3.5.6-1.fc11 Firefox/3.5.6 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc11 Thunderbird/3.0.1vv Even though this is reported against Linux, this happened on Windows XP too. None of the versions prior to this last update caused the problem. After deleting some messages, I ran Compact Folders. Many of the folders then showed up as having unread messages. All the messages in those folders had been read. Marking the folders read sometimes takes multiple tries to get all the messages marked as read. Then compacting the folders causes the messages to be marked as unread again. Reproducible: Always Steps to Reproduce: 1. Compact folders 2. 3. Actual Results: Messages that were previously read are marked unread. Expected Results: Compacting folders should not modify the status of the messages in the folders. This does not seem to happen to messages in the inbox, only to messages that are archived or saved in other folders. This happens when using the Thunderbird client to connect and compact folders on more than one imap server.
Show "Order Received" column(UID of mail if IMAP) and get screen shots "before comact" and "after compact" to know which mail's read/unread was changed. And get IMAP log for "compact", check IMAP level flow. > https://wiki.mozilla.org/MailNews:Logging Timestamp of log may help your log check. > http://www.mozilla.org/projects/nspr/reference/html/prlog.html#25328 If and only if Tb's fault is seen in log, attach(never paste) log file to this bug, after replacing sensitive data by strings with keeping string length and consistency in log data.
bug 540554 will also explain how to work around this...
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.