Hi all,

I've been making progress with TB!'s IMAP and how I can maximize on it
with a slow connection.

While in the UK, I got the opportunity to work with my IMAP server
from a remote location. I decided to play it safe and not set any of
the subscribed folders to sync automatically.

Header syncs would be initiated only upon selecting the folder. The
same for message body retrieval. This worked well from the UK.

At work where the connection is much slower, I tried the same system
and it worked yesterday pretty well with the only problem being that
if something else was being done, like an IMAP folders scan to update
counts, this would seriously interfere with what I was immediately
doing. This didn't occur with ThunderBird since that would occur
through a different connection. BTW, TB!'s connection and interaction
with the server, i.e., retrieving headers etc. is as fast as they
come. The fastest I've encountered is ThunderBird and TB! is up there.

The problem now is that despite reading a lot of TBUDL messages from
work and seeing them marked as read and remaining marked as read even
after repeatedly updating the header counts, I returned home to see
the Unread message count for TBUDL as something like:

4 <49>

The 4 represented the messages I had not read from work. The 49
represented the messages that I had read from work which were now
*still marked unread when using TB! at home*. I had to quickly go
through them to mark them as read, a POP-like experience. I never
experienced this with ThunderBird. When a message is marked read using
ThunderBird at work, it's *marked read*. When I reach home, TB! always
updates to reflect all that had been done using ThunderBird at work.

Something is amiss here and I wonder why ThunderBird get's it right
while TB! doesn't. Again, despite scaling down the activities, TB!'s
reliability falters on a slower connection in that I read mail at work
and it's not reflected on the server as it should be so that when
using another client from another location, what I've been doing at
the original location isn't properly picked up.

It's this sort of flaky behaviour that needs ironing out. I'm willing
to do whatever is reasonably possible to help get rid of it.

-- 
-=[ Allie ]=- (List Moderator and fellow end-user)

PGPKeys: http://key.ac-martin.com
Running The Bat! v2.11 Beta/5 on WinXP Pro (SP1) 

Attachment: pgpF6v22BZgWf.pgp
Description: PGP signature

________________________________________________________
 Current beta is 2.11 Beta/5 | '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/

Reply via email to