Closed Bug 655605 Opened 14 years ago Closed 14 years ago

Automatic Update All Mail Both Active and Saved Deleted

Categories

(Thunderbird :: General, defect)

x86
Windows Vista
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mrcceo, Unassigned)

Details

(Keywords: dataloss)

User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2) Build Identifier: 3.1.1 Upon restart after Thunderbird performed an automatic update to 3.1.1 all my mail both active and saved in folders on both my computer and on the AOL server were deleted!! Reproducible: Always
What is TB release before you update to TB 3.1.1?
Severity: normal → critical
Keywords: dataloss
No it was not the TB release. It was a standard release copy.
(In reply to comment #2) > No it was not the TB release. It was a standard release copy. Sorry is my mistake, I mean: you have update from TB version x.y.z to TB 3.1.1: what is your previous release x.y.z?
Are you sure your profiles where deleted (profiles can be found at http://support.mozillamessaging.com/en-US/kb/Profiles) ?
Checked profiles and there appears to be data in the folders at Imap.aol.com If that is the missing e-mails the program is not accessing the data.
5/9/11 E-mail populated itself. I did not restart the computer or close and then reopen the program. It just seemed to do it on its own.
(In reply to comment #6) > 5/9/11 E-mail populated itself. I did not restart the computer or close and > then reopen the program. It just seemed to do it on its own. So your problem is fixed ?
Problem seems fixed for now but I would like to know what caused it. That was alot of information that could have been lost.
SO when ever is happens again , look into the error console. And look on disk (we have log files for the update process ) for logs and files.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.