How can prevent Thunderbird from removing 'unread' status from mail message if it is moved to another folder?
The installed version of Thunderbird is 31.6.0. I have a lot of folders in my IMAP account to organize my emails.
Since one of the later versions of Thunderbird moved emails loose their 'unread' flag. (sorry - I can not say since what exact version this happens)
Since I have a tree view of all folders with unread mails (the caption is 'Ungelesene Ordner' in my localized installation) for my daily use, it would be very very helpfull to retain the 'unread' status in moved mails.
One other user experience aspect is in my eyes: If I want to move it, I don't want to mark it read.
Mafitar da aka zaɓa
My fault. Sorry.
I extensivly use a plug-in called 'Schnelles Nachrichtenverschieben'.
I missed, that it has the ability to mark a message as read, if it moves the message. That option seems to me to be set to 'true' after an update of that plug-in.
So - this problem is solved.
Karanta wannan amsa a matsayinta 👍 0All Replies (3)
This is what occurs with me - although I have a POP mail account.
If I use drag and drop to move an unread email to another folder, it will change to 'read' status because the left click is also interpreted as a select - it shows in Message Pane - and I have settings to auto mark as read immediately on select.
However, if I use right click on email in list and select 'Move to' and specify account and folder, then it does not change status - it remains bold, unread.
OK, good point: I do not have the message pane open, so it should not be marked read automaticly.
It happens if I right click the message and use the 'Verschieben in' (should be the translation of 'Move to') menu. I have two Thunderbird installations on two computers (Windows 7). Both act this way.
I tested drag & drop and you are right. That works as I would expect it: the unread mail stays unread (bold).
Zaɓi Mafita
My fault. Sorry.
I extensivly use a plug-in called 'Schnelles Nachrichtenverschieben'.
I missed, that it has the ability to mark a message as read, if it moves the message. That option seems to me to be set to 'true' after an update of that plug-in.
So - this problem is solved.