Closed Bug 479207 Opened 16 years ago Closed 12 years ago

Message aging / retention (delete messages more than N days old) doesn't work

Categories

(Thunderbird :: Folder and Message Lists, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: chongjin.liu, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.1b2) Gecko/20090211 Firefox/3.1b2 Build Identifier: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.1b3pre) Gecko/20090209 Lightning/1.0pre Thunderbird/3.0b1 After set the 'Delete messages more than N days old', it doesn't work. Reproducible: Always Steps to Reproduce: This test assumes that you have built up about 10-15 messages in your inbox. 1.Go to "Tools->Account Settings and then "Disk Space" for Local Folders/POP mail or "Offline and Disk Space" for IMAP and newsgroup accounts . 2. Check the radio button that says "Delete messages more than "XX days old" and enter 1 or 2 as the value. 3. Restart Thunderbird. Actual Results: after step 3: The messages more than XX days old are still there. Expected Results: after step 3: The messages more than XX days old should be deleted.
> 1.Go to "Tools->Account Settings and then "Disk Space" for Local Folders/POP mail or "Offline and Disk Space" for IMAP and newsgroup accounts . > 2. Check the radio button that says "Delete messages more than "XX days old" and enter 1 or 2 as the value. There is "per folder setting" for it. Above "per account setting" is applied to a folder only when you chose "Use server defaults" at per folder "Retention Policy". What is your per folder "Retention Policy" setting?
I can reproduce this bug in Opensolaris 111b. The version of thunderbird is 3.0b2
Status: UNCONFIRMED → NEW
Ever confirmed: true
I wonder if this is Solaris-specific.
Version: unspecified → Trunk
I believe we have duplicate of this on RHEL ... https://bugzilla.redhat.com/show_bug.cgi?id=506050
sorry, I forgot to add that we have it on thunderbird-2.0.0.22-2.el5_3
sorry, I forgot to add that we have it on thunderbird-2.0.0.22-2.el5_3. Is it possible?
Oh boy, I am sorry, proper downstream is https://bugzilla.redhat.com/show_bug.cgi?id=506051
Ran across this in Litmus testing: https://litmus.mozilla.org/show_test.cgi?id=5644 (Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.8) Gecko/20100216 Lightning/1.0b1 Thunderbird/3.0.2 ID:20100216161403). Marking blocking, even though strictly speaking it's already a known bug.... (This appears to be a cross-platform bug.)
Blocks: 548457
OS: Solaris → All
(In reply to comment #8) There at least three cases for this kind of report; (1) "per folder" property == don't delete, so msgpurge won't happen (2) Problem like bug 525622(already closed as WORKSFORME). (3) Phenomenon found in bug 525622. (see bug 525622 comment #14, please) User watches for shorter than mail.purge.min_delay=480(min), so msgpurge is not observed by user. Nathan Tuggy, what is your base or evidence that this bug is never above three kinds of report? I don't get answer for (1) or not from bug opener yet.
(In reply to comment #9) > (In reply to comment #8) > (3) Phenomenon found in bug 525622. (see bug 525622 comment #14, please) > User watches for shorter than mail.purge.min_delay=480(min), > so msgpurge is not observed by user. My apologies; the Litmus test did not mention min_delay, and I fell afoul of it without realizing. Will file corrected bug on fixing the test.
No longer blocks: 548457
OS: All → Solaris
To emily.chen@sun.com who changed this bug from Status=UNCONFIRMED to Status=NEW on 2009-05-27: Your confirming ordinally means that you could reproduce problem of this bug by a reliable "steps to reproduce problem". emily.chen@sun.com, with "what problem with what conditions with what procedure" could you reproduce? Absolutely same as comment #0? If you could see phenomenon of "Message aging (delete messages more than N days old) doesn't work"(==bug summary), what is your base/evidence that phenomenon you saw is absolutely same phenomenon as bug opener saw(==comment #0), even though no response from bug opener to question of comment #1? (such bug handling is ordinal way in sun.com?)
Hi WADA, I change to confirmed because I can reproduce it, sorry I didn't leave comments. I tried gmail, I set below setting: 1. Account setting, go to gmail, Synchronization & Storage -> Check: Delete messages more than 100 days old 2. Go to Gmail inbox folder -> Right click -> Properties -> Retention Policy , check: use my account setting After restart thunderbird 3.0, the email older than 100 days is still in Inbox.
(In reply to comment #12) > After restart thunderbird 3.0, the email older than 100 days is still in Inbox. As I wrote in bug 525622 comment #14, I could observe automatic purge of mail first time when I kept Tb ruuning all night. emily chen, can you check with small mail.purge.min_delay (and shorter mail.purge.timer_interval)?
mail.purge.min_delay = 480 mail.purge.timer_interval = 5 Now I understand the cause for this problem. Another thing I observed that : The first time I set "Delete messages more than 100 days old" it works immediately; Soon, I set "Delete messages more than 50 days old", it doesn't work at once, does it mean I need to wait 480 mins to make it work ?
wada ^ comment 14 rsx11m does https://litmus.mozilla.org/show_test.cgi?id=5644 look better? (none of the recent testcases are marked failed)
(gangyang no longer uses solaris and liuchongjin's address is dead) not solaris specific, right?
OS: Solaris → All
Summary: Message aging (delete messages more than N days old) doesn't work → Message aging / retention (delete messages more than N days old) doesn't work
i changed a test imap account to delete older than 100 days, and copied some old messages to it. set purge.min_delay to 1. messages are not deleting :(
Hi Wayne,I just try this on Thundebrird 17.0 ESR, on both Linux and Solaris, the bug is gone, I can not reproduce it.
Can not reproduce this bug with both 'account settings' and folder specific settings on TB17.0 ESR. Wayne, if you also can not reproduce it on latest TB version, you can close this bug now.
Thanks emily
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.