Closed Bug 297694 Opened 20 years ago Closed 19 years ago

Replaced inbox after quarantine causing incorrect new mail counter and slow operation

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: jhouse, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Something has broken inside thunderbird, and I don't know how to fix it.

I've had issues in the past where a virus scan has found a virus in my inbox and
quarantined the entire thing.  What I've done in this case is to close Mozilla
and restore the inbox (overwriting whatever new one Mozilla created).  I've done
this before without any major problems.  (new e-mails downloaded via POP were lost)

This most recent time, something has gone seriously wrong.  Thunderbird insisted
that I had 2 new messages.  Eventually changing view to all then unread got the
counter cleared.  Closing and reopening Mozilla showed 2 unread e-mail again (in
my default view).  Compacting the mail folder, downloading new e-mail, or
looking at the inbox when opening Thunderbird seems to take forever (minutes)
when it used to be a second or two.

It also seems like there are time periods where Thunderbird isn't updating the
mail file.  I can click on messages and view them despite an hour glass that
sometimes is there.  It doesn't however update the read/unread status.  Marking
an e-mail as junk does make a trash can icon apear but doesn't move the mail to
trash (I have it set to do that).

How can I trick Thunderbird to fix itself?  It's barely useable in its current
state.

Reproducible: Didn't try

Steps to Reproduce:
1. Receive an e-mail virus
2. Get quarantined by virus software
3. Possibly receive new mail and/or creation of a new inbox
4. Close thunderbird
5. Restore inbox
6. Open thunderbird and try to use it.

Actual Results:  
All hell breaks loose
* Several minutes to refresh inbox
* Ability to read mail but not delete mail or mark as read
* Incorrect new mail counts
* Summary data changes between closing thunderbird and opening it again

Expected Results:  
Acted like it used to
did you try removing Inbox.msf?
Deleting inbox.msf may have fixed it.
(In reply to comment #2)
> Deleting inbox.msf may have fixed it.

If it did go ahead and mark this as INVALID.

I don't think marking this bug as invalid is correct unless the following bugs
already exist:
1. Thunderbird does not detect and correct an MSF file automatically
   (Maybe a CRC on the MSF file?)
2. Thunderbird corrupts MSF file when (POP3) mail folder gets quarantined
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/
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
You need to log in before you can comment on or make changes to this bug.