550108 - All messages, are changed to "read"

Status: RESOLVED INCOMPLETE

(Thunderbird :: Folder and Message Lists, defect)

Description

[David]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.9.2) Gecko/20100115 Firefox/3.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3

Even setting reading in advanced options "Automatically mark messages as unread" is unchecked, all messages in the mailbox are changed to "read" after a few minutes of receipt.

Reproducible: Always

Steps to Reproduce:
1.Always
2.
3.



This happened with version 3.0.1 also, the first version intaled in this PC.

Comment 1

[Nathan Tuggy (:tuggyne)]

Can you verify that no other email clients (webmail, Outlook, etc) are accessing that account at the same time?
Is this an IMAP account or POP, or some other protocol?

Comment 2

[David]

Some messages manually marked as unread remain as unread.

Comment 3

[David]

I use POP.
Yes, there are other PC that access this account. 
It use a old version of Thunderbird, versão 2.0.0.23 (20090812).
But it dont have problem with the read/unread messages.

Comment 4

[Nathan Tuggy (:tuggyne)]

(In reply to comment #3)
> I use POP.
> Yes, there are other PC that access this account. 
> It use a old version of Thunderbird, versão 2.0.0.23 (20090812).
> But it dont have problem with the read/unread messages.

If it's accessing your account at (roughly) the same time, it's possible that this is interfering and marking messages as read. If possible, make sure no other computers are accessing the account while you send yourself several test messages and wait the usual amount of time it takes for messages to get (spuriously) marked read.

Comment 5

[Wayne Mery (:wsmwk)]

David, did you get this sorted out?

Comment 6

[Wayne Mery (:wsmwk)]

no response, so => incomplete. if you disagree and still see the problem using the most recent version of thunderbird, please follow the advice above, and comment in the bug.

*note however* iirc there have been other bugs on this subject, but perhaps different circumstances