All users were logged out of Bugzilla on October 13th, 2018
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 If an IMAP folder "Spong" is synchronized for offline use, it acquires a "Spong" file in addition to the usual "Spong.msf" file in the relevant directory tree. Subsequent deselection for synchronization does not remove this file, and hence does not clear the expected disk space (perhaps needed by the user for something else). Note that manual removal of the "Spong" file does not always seem to work - not that this would be an adequate solution for ordinary users! I have seen it recreated (though not always) on entering that folder, still deselected. A workaround for subfolders is to remove the directory corresponding to the containing folder (if you don't mind losing all information about those messages, at least temporarily). I haven't risked doing that at the top level, though, i.e. removing the directory named for the IMAP server itself. Needless to say, the above manual hacking should be done with Mozilla not running! Reproducible: Always Steps to Reproduce: 1. Select a folder for offline sync 2. Sync 3. Deselect the folder Actual Results: Disk space used at 2 but not cleared at 3 Expected Results: Cleared the disk space
actually, this is not neccesarily true - you could temporarily set a folder as not for offline use without wanting all the offline messages deleted...you're right that this is probably what most people want, though.
Status: UNCONFIRMED → NEW
Ever confirmed: true
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
I have: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Thunderbird/3.0b2 Actually the problem is a little more complex: it is not possible to password protect offline IMAP messages. One can use a master password, but if you want to protect only one of many accounts (e.g. company vs. private mailbox, same machine), then there is no way. I tried to set the config parameter "mail.password_protect_local_cache" to "true", which only *seems* to work, but it doesn't as: when I click on my Inbox, I get a prompt for my password (so far, so good), but if I hit Cancel(!), once again I see my e-mails.
Well, I do not want allready loaded offline messages to disappear, I just do not want download all those old mails. Sorry if this is making all harder.
(In reply to Ilari Halminen from comment #4) I don't think I understand your use-case. You can use the "Disk Space" options to select which messages to download whilst sync'd, e.g. only the most recent ones. You can then (because of what I am here calling a bug) preserve this set exactly by un-syncing. But if you left it sync'd you could continue to prevent old mails from being downloaded, and if you ever wanted to change the set at all you would have to resync anyway. Are you wanting a new "Disk Space" rule such as "download only viewed messages" (like cacheing rather than pro-active syncing, although would still need to check for consistency in case previously downloaded messages had changed in the mailbox)?
You need to log in before you can comment on or make changes to this bug.