Closed
Bug 301483
Opened 19 years ago
Closed 17 years ago
New messages don't appear in the individual folders.
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: dloomis.nh.ultranet, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Build Identifier: Mozilla 1.7.8 While I'm running Mozilla, I get an audible tome, my unread message number increments, but when I go to look at the message in the individual folder they are not displayed. Reproducible: Always Steps to Reproduce: 1. I have no idea how you would replicate the problems without using my computer, as the problem seems to be in this computer. 2. When I have the mail reader open new messages show up in the left side of the window and their receipt is indicated by an annunciator tone, but the don't show up inside the individual folders. 3. Actual Results: When I have the mail reader open, in the background - i.e. while doing other work on the computer, the receipt of new messages is indicated by an annunciator tone, the unread messages number increments upwards in the left side of the window but the unread messages don't show up inside the individual folders. This also occurs when I am reading the messages in one folder and new messages arrive and remain in the In Box, or are filtered to other folders. Expected Results: When a new message appears, I should get the annunciator tone, the number of unread messages in the specific folder should increment upwards, and the unread message should be available to read in the specific folder. I am using a standard ver 1.7.8 of Mozilla, which have reinstalled several time, and still get the same indications. I can't qualify the importance of this bug as I feel it sits somewhere between Normal and Major. I can not read many new messages I have received, and have no idea if they are SPAM which I would gladly do without, or important messages having to do with my medical care, newly scheduled appointments or meeting of which I should be aware. I currently show 10 unread messages in my Inbox that I can neiter read nor dispose of in any way that I know of, and another 34 unread messages in my Junk folder, which I can not view to determine if they really are junk messages or merely ones that my filters have tagged as junk by mistake.
I guess your index files are corrupt. Please close Mozilla completely and go to your Mozilla profile folder. There go to the mail subfolder and deeper to the folder for your account. Please make a backup copy of this folder before you go further. Now delete the *.msf files (only these!), the index files. Restart Mozilla and see if it now works.
URL: N/A
Version: unspecified → 1.7 Branch
answer from reporter: That's about what I figured after I found the same problem in Mozilla, Netscape, and Thunderbird. I'm running Thunderbird now, and things seem to be OK. Thanks, Dave So I resolve this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
So this seems not to be only a one time corrupt index file. I reopen the bug to
let other people decide.
from reporter:
I understand what you are saying, but although I have tried this several
times, thoroughly wiping out what should be the program's corporate memory, I
still have new files that I can not access. i.e. I completely kill Mozilla,
blow out the *.msf files, reboot Mozilla, and some of the new files are still
there. Sometimes killing the index files, compressing the folders and going
back to the offending folders works, but this isn't a very reliable way of
clearing the problem.
In the past I have had problems retaining the index file for the Inbox
folder, now I have difficulty clearing these index files for many of the
folders, and yes, I am going to the right folder as indicated by unique folders
I have created to insure that I am working on the right files.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Comment 4•17 years ago
|
||
(2.5+ years later) MozillaAS v1.7.x is not supported anymore. (Would have been "Incomplete", now is) R.Invalid. Reopen if you can reproduce with SeaMonkey v1.1.9.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 17 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•