368041 - Marking thread as Read on IMAP doesn't mark all messages read

Status: RESOLVED FIXED

(Thunderbird :: Mail Window Front End, defect)

Description

[David Fraser]

If I use the "T" keyboard shortcut to mark the remainder of a thread as read, and skip to the next unread thread:
  - the messages initially appear read in the thread list
  - when resyncing with the IMAP server they become unread again
It seems that they are not being properly marked as read on the IMAP server
I am using Zimbra as my IMAP server

Comment 1

[Vlastimil Babka]

I can confirm this, happened with all 2.0 beta versions I've used and also in rc1. Using Gentoo Linux. Using two different external IMAP accounts so I don't know server details, but IMHO it's not related to them.

Comment 2

[David :Bienvenu]

darn, that bug has been there forever...fix upcoming...

Comment 3

[David :Bienvenu]

Attachment: proposed fix

ApplyCommandToIndices will also mark the messages read on the server...

Comment 4

[David :Bienvenu]

fixed on trunk

Comment 6

[David :Bienvenu]

Comment on attachment 261263 [details] [diff] [review]
proposed fix

straightforward fix, and I've just had a dup filed on 2.0 about this.

Comment 7

[Daniel Veditz [:dveditz]]

Comment on attachment 261263 [details] [diff] [review]
proposed fix

approved for 1.8.1.4, a=dveditz for release-drivers if you can land it today

Comment 8

[David :Bienvenu]

fixed on 1.8.1 branch

Comment 9

[Jay Patel [:jay]]

v.fixed with version 2.0.0.4pre (20070504)

Comment 10

[Jim Michaels]

I don't know if this is related, but currently, this fix might be marking all messages as read when I mark a range of messages as read. this just happened to me and there's no undo.
separate bug?

I think the intent was to mark all messages in the *thread* not all messages in the account! please fix. this is just insanely broken. I have tb 24.6.0

Comment 11

[Kent James (:rkent)]

Jim, this is an old bug that was resolved long ago. If you have a current issue, please file a new bug. If you want to relate the issue in the new bug as a regression from the fix in this bug, then mark the new bug as blocking this bug.