Closed
Bug 267718
Opened 20 years ago
Closed 20 years ago
Messages disappearing from inbox folder, but that can be found performing a search
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 267719
People
(Reporter: carlo_rocchi, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Build Identifier: thunderbird version 0.8 (20040913) NOTE: I am using GLOBAL INBOX I have noticed in a few occasion that I download mail, I can see the message in the Inbox window, than the message disappears (of course I did not delete it). If I remember who the sender was or some words in the message, I perform a search and I can see the messages in the search results. If I set the message as UNREAD, it shows up again in the inbox window, but just if I set the option View:Unread, otherwise it is still invisible. If i mark the message UNREAD again, it disappears from inbox window but it can still be found performing a search. The message is actually in the inbox file (it can be found opening the file with a text editor) and I did not notice anything strange in it. Reproducible: Didn't try Steps to Reproduce: well, i cant reproduce it really; it has happened a couple of times (that I realized). Hopefully I havent lost many messages I'm not aware of! I experienced this problem both under windows 2000 and Fedora Core 2. I am using the default theme. As far as severity is concerned (see next section), I consider the bug as a potential data loss problem, since you may not notice you received that message, so you dont realize it has disappeared. Sometimes you receive dozens messages, you dont read them immediatly, so if one or two disappear you may not notice it later. Of course you might not know any keyword to perform a search, so your message is virtually lost.
Comment 1•20 years ago
|
||
*** This bug has been marked as a duplicate of 267719 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•