186300 - Deleted email reappears in inbox after client or system crash

Status: RESOLVED WORKSFORME

(MailNews Core :: Database, defect)

Description

[Dan Brusca]

User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.2.1) Gecko/20021130

Email received on 4th June 2002 reappears in the inbox following a system crash
or forced closure of Mail using Ctrl+Alt+Del when the program has stopped
responding.

The program will also spend several minutes 'Building summary file for inbox' on
relaunch.

Problem observed countless times since v1.0

OS: WindowsMe

Reproducible: Couldn't Reproduce

Steps to Reproduce:
Reproduction of error dependant on system or program crash.

Comment 1

[David :Bienvenu]

If it's just that message, somehow it got into your mailbox without an
x-mozilla-status line, so we don't know that it's been deleted, when the
INBOX.msf file gets regenerated. You could open the INBOX with a text editor and
add an x-mozilla-status line to the headers for the message in question. Or,
using Mozilla, you should be able to delete that message, and then compact your
INBOX, and the message should be permanently gone.

How big is your INBOX file?

Comment 2

[Colin S]

This problem also occurs on my system, WinXP build 2003071814. It does not occur
only when the program crashes. It seems to occur rather randomly, but one
behaviour that occurs is that the INBOX list is always blank when Mail &
Newsgroups is opened. Clicking on the INBOX to fix this blank listing causes
these emails to be re-added.

This perhaps leads to a more important security issue: Why are deleted emails
not being deleted??

Comment 3

[David :Bienvenu]

you have to compact folders to remove deleted mail, because we use the standard
berkeley mailbox format.

what program did you import your e-mail from? If it was Outlook Express, this
bug is fixed, in that I've fixed outlook express import to add x-mozilla-status
lines to imported messages.

Comment 4

[David :Bienvenu]

no response, marking wfm - I'm pretty sure this data must have been imported
from outlook/outlook express before the import bug was fixed.