Closed
Bug 267338
Opened 20 years ago
Closed 17 years ago
Thunderbird continuously rebuilds summary files for sent items, resulting in duplicate messages that are marked unread
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: pat, Assigned: mscott)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Build Identifier: Thunderbird 0.8 When starting TB, summary files for "Sent" Items are rebuilt. The message counts are therefore incorrect, and also are marked as "Unread". Attempted to remove and rebuild the msf files, however, the behavior continues to repeat itself. Reproducible: Always Steps to Reproduce: 1.Simply starting TBird produces the activity. 2. 3. Actual Results: Please see above for brevity's sake. Expected Results: Sent Items folder should maintain correct message count and read status. none at this time
Comment 1•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
*** Bug 319982 has been marked as a duplicate of this bug. ***
Comment 4•19 years ago
|
||
I saw this for the first time this morning. TB constantly rebuilt the sent items.
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
Summary: Thunderbird continuously rebuilds summary files for sent items, resulting in dupilcate messages that are marked unread → Thunderbird continuously rebuilds summary files for sent items, resulting in duplicate messages that are marked unread
Comment 5•19 years ago
|
||
It is not just sent folder; in most cases I know about (over 50!) there is same problem with indexing in inbox folder. Slower computers (cpu 350 - 800 MHz), mailbox over 1 GB (large attachments) can not rebuild indexes until you move all mail to new folder and delete problematic foder (not in Thunderbird!). After this procedure mail can be moved back to foldel (if inbox or sent, they are created automatical). More save procedure is to move old mail in separate folder, so each file (folder) is not too big. What is too big depends on cpu, memory, system... Problem regulary reappears when folder grows over acceptable size and is connected with bugs, descriped as reappearing deleted mail after raindexation.
Updated•18 years ago
|
QA Contact: general
Comment 6•17 years ago
|
||
Ray, Pat, do you still this problem using current version?
Comment 7•17 years ago
|
||
No additional useful information since last comment -> resolving incomplete. Please comment if the issue still occurs in the latest supported 2.0.0.14 / trunk nightlies.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 17 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•