Re: 3.0.2.4: VERY Weird Behavior Duplicate Behavior, and Threading

[Keith Russell]

Hello, Allie.
I thought I had sent this off an hour ago, and I just discovered
SEVENTEEN copies in my Outbox! How did that happen?!!!
And after trying again to post using TB!, I now have two more. 
:-( One has an icon in the second column; the second doesn't. 
(What is that, anyway?) As a result, this reply will be sent 
using Mulberry.

On Sunday, October 31, 2004, 9:56:09 PM, you wrote:
On Sunday, October 31, 2004 at 11:49:01 PM [GMT -0500], Keith 
Russell
wrote:

Someone (Allie, I
think) suggested that they might be due to the large number of
messages I have on the server. This seemed strange to me, 
since, with
POP3, at least, users tend to rave about The Bat's 
performance with
large message bases.

  IMAP is different from POP3. With POP3, you're working with 
a message
  base stored locally. With IMAP, your message bases are 
stored on the
  server. You keep syncing them with a local cache 
representation that
  needs updating to reflect what's currently on the server. 
Syncing a
  large message base takes longer than syncing a small message 
base.
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.
Worse yet, I sometimes click on a message and get the wrong 
body!  I
just displayed five unread messages in a folder. Of the five, 
I was
only able to read one. The other three all linked to the wrong
message.

Now that's really odd. I don't really have an explanation for 
such
behaviour.
So obviously, you haven't seen this. Has anyone else?
I have problems with Mulberry. You're having problems with 
TB!. IMAP
needs good client/server compatibility to work well. You may 
find that
your client of choice depends on how well it works with your 
IMAP
server. MDaemon, my own IMAP server is more TB! than Mulberry 
friendly.
Lucky me.
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.
In addition, earlier today I had something VERY strange 
happen as I
was reading a thread from one of my Yahoo groups. I was 
getting "No
message loaded" for quite a few of the messages in the 
thread. This is
something I've seen quite a bit, but it had always seemed to 
be random
(and VERY frustrating).

Quite often, the 'no message loaded' is associated with TB! 
being quite
busy at working with its queue of tasks. You then have to wait 
for
those tasks to complete. Unlike Mulberry and ThunderBird, TB! 
works via
a single connection to the server. One of TB!'s future 
development plans
is support for multiple connections to the server.
Yes, but of course Mulberry's big problem is lack of
multithreading....
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?
However, I discovered that when I looked at the same thread in
Mulberry and Thunderbird, the problem messages were not 
listed at all
in the message list. As I looked further, I found that I had 
two
copies of every message. All were sent on October 19th. 
However, one
copy of each, according to the "Received" column in TB! and 
Mulberry,
was received on the 19th and the other was received on the 
22nd. In
each case, the copy received on the 19th was a problem 
message, while
the one received on the 22nd was normal.

Did you try deleting your local cache for that folder/mailbox?
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!
I cannot
find the "Received" date and time (in the "Received" column) 
anywhere
in the message headers. Can anyone tell me where this 
information
comes from? Since it's identical in both TB! and Mulberry, it 
must be
in the message somewhere, but where?

The received time in the TB! received column is the time the 
message was
received by TB! and not the server. You'll therefore not see 
that time
in the message header.
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.
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 do a lot of things that we take for 
granted with
TB!.
Very true.
I also continue to be frustrated that TB! does not allow 
threading on
both references and subject. In my thread of six good 
messages, when I
thread by reference, four thread properly and two do not, 
because they
don't have reference headers. All six thread properly in both
Thunderbird and Mulberry.

Yes. I don't know when TB! will start threading using both 
subject and
references.
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?
Thanks for the post. Very helpful, as always.
--
Keith Russell
...Time flies like the wind--fruit flies like bananas!
Using The Bat! 3.0.2.4 Rush under Windows XP 5.1 Build 2600 on a 
2.4 GHZ Pentium IV with 512 MB.

________________________________________________________
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/