Red Hat Bugzilla – Bug 532915
Thunderbird 3.0 Beta 4 applies retention policy to all folders
Last modified: 2009-12-05 15:31:33 EST
Description of problem:
The Thunderbird installation on this system is set to use an IMAP server with several folders:
If one right clicks on Bar and selects Properties in the context menu one can set a retention policy for a folder.
As it is set on a folder basis it is implied that this rule only applies for that one folder.
If one checks the retention policy for every any folder though, one sees that this new policy has been set globally for every single folder, deleting mail one might wanted to keep.
Version-Release number of selected component (if applicable):
We filed this bug in the upstream database (https://bugzilla.mozilla.org/show_bug.cgi?id=527267) and believe that it is more appropriate to let it be resolved upstream.
We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.
Thank you for the bug report.
*** Bug 528229 has been marked as a duplicate of this bug. ***
The bug can destroy users' data. I'm all for working with upstream, but we need to get the fix into Fedora with all speed.
From the upstream bug, it looks like the issue is resolved. Can someone confirm that we have the fix? If not, can we get a new build?
I can confirm that this bug is _NOT_ fixed in fedora.
This bug bit me hard. I tried to change the retention policy on an IMAP folder for some disposable list mail, and it applied the retention policy to my Archives folders, too. It deleted all of my archived mail, except the last 2000. This is a serious problem. Please push on this.
(In reply to comment #4)
> I can confirm that this bug is _NOT_ fixed in fedora.
No, it hasn't been fixed in bugzilla, read comment 1 once more please. And yes I was bitten by this myself and I lost some important mails because of this.
Matej, the upstream bug you referenced in comment 1 is closed as a duplicate of upstream #515316, which is itself in the 'RESOLVED FIXED' state and has an attached patch. From the comments, the fix is checked in and seems to resolve the problem.
Given that, it really seems like we ought to pull in the fix. If the fix is inadequate in some way, then we really need to let upstream know.
If there is some other upstream bug or discussion that we are blocking on, then please link.
It seems a fix has been created for almost 2 months now:
David :Bienvenu 2009-10-09 06:39:12 PDT
fix checked in.
It puzzles me why such a significant bug is still left unpatched. I use mainstream Fedora 11 and I have to put up with beta versions on a main distribution.
This is a great advertisement to use anything but Fedora if you will not even try to import upstream patches: https://bug515316.bugzilla.mozilla.org/attachment.cgi?id=405334