User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.9) Gecko/2009040821 Firefox/3.0.9 (.NET CLR 3.5.30729) Build Identifier: 2.0.0.21 (20090302) When I go to mark a message as read and during that time it marks it as read automatically, it then will mark it as unread which is not what I would expect. Same thing if I want to mark a message as unread and it is already unread, it then gets marked as read. The same thing happens when marking a bunch of messages as read or unread and some of them have already been marked, then sometimes they get all marked as unread which I actually meant for them to be marked as read or the opposite happens and they all get marked as read when I meant for them all to be marked as unread. Reproducible: Always Steps to Reproduce: 1. Mark 1 message as read when it is still unread. 2. Try to mark that same message as read again and it gets marked as unread. 3. Repeat with setting the message to unread this time and they all get marked to read instead. 1. Mark 2 of 3 messages as unread and 1 message as read and then highlight them all. 2. Try to mark them all as read and they all get marked as unread instead. 3. Repeat with setting the messages to unread this time and they all get marked to read instead. Actual Results: 1st test in step 2 the message gets marked as unread instead of red and in step 3 the message gets marked as read instead of unread. 2nd test in step 2 the messages all get marked as unread instead of read and in step 3 all the messages get marked as read instead of unread. Expected Results: 1st test in step 2 the message should get marked as read every time and in step 3 the message should get marked as unread every time. 2nd test in step 2 all the messages should get marked as read every time and in step 3 all the messages should get marked as unread every time. This should also apply to setting a message as being replied to or forwarded to as well in the same function, never undoing what was done but always doing what you set it to even if it was already set to be that. If this is implemented, then this will match the functionality that other email clients like outlook, outlook express, and eudora provide.

(In reply to comment #0) > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.9) > Gecko/2009040821 Firefox/3.0.9 (.NET CLR 3.5.30729) > Build Identifier: 2.0.0.21 (20090302) > Steps to Reproduce: > 1. Mark 1 message as read when it is still unread. > 2. Try to mark that same message as read again and it gets marked as unread. > 3. Repeat with setting the message to unread this time and they all get marked > to read instead. > 1st test in step 2 the message gets marked as unread instead of red and in step > 3 the message gets marked as read instead of unread. The behaviour that you describe is deliberate: the menu item that you use for read\unread message has two state (on\off): if the message is read, click on it cause unread status (menu item not is flagged on the left) and viceversa if message is unread click cause read status (menu item is flagged on the left). You cannot > 2. Try to mark that same message as read again and it gets marked as unread. because the menu item not is flagged, and this action is equals to mark message as unread. Here with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1pre) Gecko/20090617 Lightning/1.0pre Shredder/3.0b3pre ID:20090617032054

I still don't understand why if a flag that is labeled as read, it is programmed to mark it as unread if the message is marked as read already. Why do you have 2 flags then, one as read and one as unread. If they are to reverse what one does depending on the status of the message, then that feature is broken. Any other email program I use flags any message as read if I select read no matter if the message is already read or not. That's why it has those 2 entries and thunderbird is the ONLY email program that does not work this way. If I select a bunch of messages, and some of those messages are read and others are unread, and then I select mark as read, I'm not gonna know what the behavior of that is gonna be. Same thing if I had selected mark as unread. The behavior needs to be consistent and it is not the way it is currently programmed. In fact someone else was frustrated with this behavior and created an addon that creates a button called mark all read. Here is the link: https://addons.mozilla.org/en-US/thunderbird/addon/2273

(In reply to comment #2) > I still don't understand why if a flag that is labeled as read, it is > programmed to mark it as unread if the message is marked as read already. Why > do you have 2 flags then, one as read and one as unread. It is a developing choise, for me is right... but I'm wait other opinions. Ciao.

maybe ludovic or wayne can take a look at this (comment #1 and comment #2).

I really would like it if this is fixed as I no longer use this feature because of its inconsistency. It would be useful again once it is fixed and I no longer need that addon then. If you have to explain a feature in order to know how to use it and it doesn't work the way most people expect, it needs to be redesigned.

Carl it seems a dupe of an open bug. Feel free to reopen it if I'm wrong.

Yeah this looks to be a duplicate. I will add my comments then to bug 327828.

Cleanup *dupeme* whiteboard flag from bugs that are marked as Resolved Duplicate!