On Monday, November 01, 2004, at 02:41 AM, Keith Russell wrote: > I thought I had sent this off an hour ago, and I just discovered > SEVENTEEN copies in my Outbox! How did that happen?!!!
Seems that you have your Outbox server side. I'd make that local, unless you depend a lot on keeping drafts available for use on your other IMAP clients. TB! is still having problems with the Outbox being used server side. I avoid doing that. > Of course. I meant to mention that, but forgot. I understand that > performance will not be as good with IMAP as with POP3. The point I > was trying to make, though, was that I would hope that TB!'s IMAP > performance would compare as favorably to other clients as does its > POP3 performance. However, where Mulberry and Thunderbird seem to be > little affected by the volume of my messages, it does appear that The > Bat! is. For some time, my experience was that with the synchronisation options for TB! set to work like ThunderBird's sync routines, their performance is about the same. Where ThunderBird get's the better of TB! is when you're forcing it to fulfil multiple requests. For example, you select a folder to update counts and sync headers and then move to another folder to continue reading new messages. ThunderBird will spawn another connection to do both tasks, while TB! will have to do all those tasks via the same connection. > Good point. I hadn't thought of server/client compatibility. This > means that if I change IMAP providers, as I may do in a few weeks, I > could find the situation reversed. Interesting. Yes. This may be the case, though Mulberry works well with the big server apps. > Yes, but of course Mulberry's big problem is lack of > multithreading.... Ah yes. That's incredibly annoying, especially on a medium to low speed connection. > I did some experimenting tonight and found that reloading the message > often displays the body. Is there a keystroke for that, so I don't > have to navigate the menu every time? How do you reload the message? I didn't know that you could reload a message from the server. AFAIK, it's downloaded once and isn't downloaded again, unless you purge the folders cache, otherwise the message is loaded from the cache from then on. > No, because I couldn't remember how. Can you remind me? > I found a couple of messages in my Inbox folder tonight that > exhibited the same behavior. Again, those with a received date > corresponding to the sent date cannot be read. Copies of the same > messages received on the 22nd are fine! A question? When you're frustrated waiting on TB!, what do you do? Do you continue waiting or do you exit and restart it in frustration. That sort of thing can really mess up the folder caches etc. > I thought at first that this was the case, but the fact that the > dates were identical for TB! and Mulberry threw me off, I guess. Both dates and times for the received columns are identical? > I'm guessing that I probably used Thunderbird for three days > before I got around to checking out TB! and Mulberry again on the > 22nd. I must have started them up at the same time so that the > received date and times would correspond. > I haven't been able to find the date Thunderbird received these > messages, because the "Date" column seems to mean the sent date, > and I don't know how to add a "Received" column. Do you? ThunderBird doesn't support that. > I assume that someone has posted this to the wish list long ago, > but is there any way I can search The Bat! Wishes (or bugtracker) > to find out? https://www.ritlabs.com/bt/main_page.php -- -=[ Allie ]=- ... Half the lies they tell me aren't true. --Yogi Berra ______________________________________________________________ Running TB! v3.0.2.2 Rush or SquirrelMail WebMail for IMAP IMAP Server: MDaemon Pro | OS: Windows XP Pro (Service Pack 2) ________________________________________________________ Current beta is 3.0.2.4 Rush | '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/
