Closed Bug 1536200 Opened 7 years ago Closed 4 years ago

Storage retention is deleting the wrong date range

Categories

(Thunderbird :: Account Manager, defect)

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: anjeyelf, Unassigned)

Details

(Keywords: dataloss)

User Agent: Mozilla/5.0 (Windows NT 6.0; rv:52.0) Gecko/20100101 Firefox/52.0

Steps to reproduce:

I have come across two issues of this, but I've not tested it myself.

Imap account
In Account Settings > Synchronisation & storage, under 'disc space' section
user selected:
'delete all but the most recent 2000 messages'

Actual results:

Result was the opposite, TB deleted the most recent 2000 messages.

Expected results:

There has been two reports of this occurance in the Support Forum.
One was a gmail server, the other a dovecot server.
Links to questions:
https://support.mozilla.org/en-US/questions/1241354
https://support.mozilla.org/en-US/questions/1253442

Could someone have a look at this as it could be a real issue of loss of emails.
Thanks.

I'll update on exact version as soon as possible as I need info from user.

Let's make a more meaningful summary.

(In reply to Anje from comment #0)

...
I'll update on exact version as soon as possible as I need info from user.

Do we have their feedback?

Severity: normal → critical
Component: Untriaged → Account Manager
Flags: needinfo?(anjeyelf)
Keywords: dataloss
Summary: Disc Space incorrect deletion → Storage retention is deleting the wrong date range

I was hoping to get info from support 125442, but nothing as yet.

Flags: needinfo?(anjeyelf)

Update: I attempted contact again and received response.
Quote:
"I was using Windows 10 with Tbird 60.6.1. I been afraid to use the feature again....."

Some other retention bug reports for your consideration https://mzl.la/2nFpRmn

Flags: needinfo?(anjeyelf)
Flags: needinfo?(anjeyelf)

both reporters have not posted again

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