Hi Allie and Terry,
--<> 31.05.2005 23:12 -0500:
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.
For me too, except the trash folder. All sent mailing lists mails get
deleted by a outgoing filter and my trash folder grows and grows.
This is a known bug. Some time ago it seemed to be fixed, but now it's
still/again there.
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!.
Hmm, not for me. I don't use synchronisation.
Open TB!, getting new messages, close TB! without reading them.
Open Mulberry, reading new messages, deleting and expunging them, closing
Mulberry.
On reopening TB! still has the bold folder for some time. But after a while
- say: after TB! has updated his whole message list for all folders - the
message is away.
It's the same, when I read a message in TB! and then do the steps mentioned
above.
Seems like a waste of bandwidth to me to reload every time.
Yes.
Oh yes. Do you, Terry, really need full synchronisation?
For me, TB! is useless with synchronisation. I get duplicate messages,
reloading is poor slow, opening messages can take forever, if TB! is
updating its list in the background.
Since I turned synchronisation off, TB! works as good as TB! works with
IMAP and I can work with it quite okay.
I reported this problem and got some confirmations. Unfortunately I can't
find it this time.
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.
I would swear this is related to synchronisation. ;)
Terry, what connection are you using? Fast or slow one?
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.
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.
You're right, Allie. Since Stefan wrote they will focus on IMAP in the next
beta cycle and said something about showing deleted messages in the
"normal" message list, this would be a thing, we can point them to.
When one is able to see deleted messages with a different colour or strike
out or something in the message list, copying to trash folder is really
useless.
--
Manuel, http://www.manuel-breitfeld.de
________________________________________________________
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/
