Closed Bug 314383 Opened 20 years ago Closed 10 months ago

unsubscribing from a newsgroup does not remove it's downloaded data

Categories

(MailNews Core :: Backend, defect)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: dirtyepic, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051029 Firefox/1.5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051029 Firefox/1.5 when you unsubscribe from a newsgroup, its .dat and .msf files remain indefinitely. this has the potential to waste a lot of disk space on useless data. i found i had 160mb worth of unsubscribed newgroup info in my profile that could have been freed. to reproduce: (using news.gmane.org as an example) - subscribe to eg. gmane.linux.kernel - download the last 10000 headers and bodies - unsubscribe from the newsgroup - notice that gmane.linux.kernel.dat and gmane.linux.kernel.msf are taking up 50mb of space in .thunderbird/profile/News/news.gmane.org i suppose this might be useful if you ever want to resubscribe, since it would save you from downloading everything again. maybe a 'Also delete saved data' checkbox on the confirmation dialog could be added. Reproducible: Always Steps to Reproduce:
Related to Core bug 185348?
This also happens with SeaMonkey on Windows, and if I remember correctly, on Mac OS X, too. Maybe some corrections to Hardware, OS and Product fields would be appropriate.
Assignee: mscott → nobody
Status: UNCONFIRMED → NEW
Component: General → MailNews: Backend
Ever confirmed: true
OS: Linux → All
Product: Thunderbird → Core
QA Contact: general → backend
Hardware: PC → All
Product: Core → MailNews Core
Severity: normal → S3

When unsubscribing a newsgroup with current Thunderbird versions, the message database (.msf) and the mailbox file are getting removed. For the filter file (.dat) we still have bug 185348.

Status: NEW → RESOLVED
Closed: 10 months ago
Resolution: --- → WORKSFORME
See Also: → 185348
Duplicate of this bug: 323815
You need to log in before you can comment on or make changes to this bug.