On Tuesday, May 31, 2005 at 5:24:18 PM [GMT -0500], Terry wrote: > IMAP account, set to delete on server. Option to compress all folders > on exit checked. Option to compress when switching between folders > unchecked. On exit, folders aren't being compressed/expunged.
That's a bummer. I compress on exiting folders and this seems to work most of the time. > Using IMAPSize, I expunge the deleted messages. When I reopen TB, I > can still read the messages in TB using browse deleted messages > function but they go away if I clear the cache, so I'm assuming that > the local cache isn't being cleared. Yes. Looks like though the message list may be synchronized on startup, with that of the server, the cached message base itself isn't. As a result deleted messages remain locally until you run a compress in TB!. > I have the folders set to full messages synchronisation. I guess the > first question is, when is the cache cleared and/or updated? The cache is updated with each synchronization. Deleted messages are removed from the cache with each compress operation from within TB!. With each compress operation, the server is also expunged of deleted messages. > I've since set clear cached messages on exit. Are there any other > settings I should check? Is it really necessary to clear all cached > messages on exit? No. It would be better to just compress all folders intermittently or just after a startup or just before a shutdown of TB!. This is because compressing on exit isn't working for you. > Seems like a waste of bandwidth to me to reload every time. Yes. > I'd expect the cache to be updated so that the deleted messages were > removed after they were expunged from the server. That seems to be > what happens when the compress folder option is used. The cache seems to be compressed, i.e., rid of deleted messages only when a local compress operation is performed. This is likely a POP3 legacy. > Other changes I make when not using TB aren't reflected as well. For > instance, I receive an e-mail, read it and then close TB. Using > IMAPSize, I delete and expunge the e-mail. When I start TB! again, the > message is removed from the inbox on the first check but the cached > version of that message is still there, even after a refresh and a > synchronize all folders. I can see it with browse deleted messages. > That doesn't seem right to me. I agree that it's not really right, but that's how it works now. Expunging on the server using another client or tool, doesn't mean that TB! will update its cache on a restart. TB! depends on you to use its own compress operations. If you did so, the cache would be up to date and commensurate with what's happening on the server. > IMAP account set to delete to local trash folder. Same thing as above > is happening, which raises another question. I would expect that > deleting to the local folder would move the message from the IMAP > folder to the local trash folder. That's not happening. It looks like > the message is copied to the local trash folder and is marked as > deleted on the server. I don't even know what to say here. AFAIK, the IMAP protocol makes the concept of a trash folder unnecessary. For example, Mulberry accounts don't carry trash folders. If you delete a message in IMAP, it's simply flagged as deleted. This is different from POP3 deletions. I know that for TB! POP3 deleted messages remain in the message base until you run a compress operation, but this isn't so for most other POP3 clients. As a result, trash folders are necessary. What TB! does here, i.e., copying the message to trash and marking the original as deleted on the server is understandable and in keeping with how the protocol functions. -- -= Allie Martin =- The Bat!� v3.5.24 System Specs: http://www.landscreek.net/sysspecs.htm -=-=- When money talks there are few interruptions. ________________________________________________________ Current beta is 3.5.24 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
