Closed Bug 1779780 Opened 5 months ago Closed 5 months ago

Corrupted emails in TB 102.0.2

Categories

(MailNews Core :: Database, defect, P1)

Thunderbird 102

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1777738

People

(Reporter: duanebrosius, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: dataloss, Whiteboard: [Repair will *not* always fix corruption])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36

Steps to reproduce:

I am using Thunderbird 102.0.2 (64-bit) and I am still having corrupted emails.

My emails are sometimes corrupted - link to the wrong emails and/or just see the code not the true email.
I try and do a "properties" / "repair folder". Some times it works but most of the time it just sits there and does nothing. I then have to exit Thunderbird and restart it then sometimes the "repair folder" will work. BUT that does not always fix all the corrupted email files.

Any ideas why we are having this issue? I know that there was a problem with an earlier release but I thought it was fixed now.

Blocks: tb102found
Severity: -- → S2
Component: Untriaged → Database
Priority: -- → P1
Product: Thunderbird → MailNews Core
See Also: → 1779741
Keywords: dataloss
Whiteboard: [Repair will *not* always fix corruption]
Flags: needinfo?(duanebrosius)

imap.earthlink.net

Flags: needinfo?(duanebrosius)

Duane, my experience is that deleting a message (by DELETE or MOVE) somehow corrupts the file. Sometimes this is apparent immediately, sometimes it's discovered later. You can run repair, then compact -- in that order -- but as you've seen, while this often works, it is not guaranteed. The corrupted message(s) may magically reappear, at the expense of one or more good messages in the vicinity that were up till then OK.

One caution to take is to go into SETTINGS and disable the new default to automatically compact without asking. Otherwise, compact may run on the corrupted file -- without you knowing -- before the folder is repaired.

See also Bug 1778241 for my running commentary on this...

Status: UNCONFIRMED → RESOLVED
Closed: 5 months ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.