Messages moved out of a folder reappear



MailNews Core
16 years ago
10 years ago


(Reporter: bugzilla, Assigned: (not reading, please use instead))


Windows 2000

Firefox Tracking Flags

(Not tracked)




16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910

It appears that moved messages don't get purged from the old storage file,
and/or message flags like 'read' don't always stick. Between sessions, messages
that should no longer be in one folder reappear unread while still available
(read) in the other folder.

Reproducible: Always

Steps to Reproduce:
I have a fairly large mail archive (3-4 years) and every now and then move
messages around between different folders. When I move a large chunk from Trash
to the self-defined Archive->Trash2001 folder, and close&exit Moz, the Trash
storage file still contains all the moved messages (i.e. it was not purged). The
old mails sometimes reappear unread, when I delete a new mail to Trash.
Actual Results:  
Mail is not purged/deleted from the storage file.

Expected Results:  
Moved mail should be purged from the old storage file, for example when closing
MailNews or closing Moz.

I use a custom store folder (under MyDocs) with subdirectories for each account.


16 years ago
QA Contact: gayatri → stephend

Comment 1

16 years ago
I've got that problem with 
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 
(with the default mail directories)
Have you tried compacting the folders and also emptying the trash?

Comment 3

16 years ago
You're right, compacting the folder solves it.
--> esther (compacting folders), I'm pretty sure this is expected behavior, but
I could be wrong...
Assignee: mscott → sspitzer
QA Contact: stephend → esther
Product: MailNews → Core
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.