On Wednesday, July 06, 2005, at 01:14 PM, Tony Boom wrote: > I've given up on it now totally. It works but it's just *so much > effort* trying to keep on top of it, keeping up with it and trying > to understand what it's doing is just too tiring. It's now telling > me half my mailboxes don't exist even though it has them in the > folder tree complete with the correct message count. It tells me I > have 80 unread messages when there are only 7 in the folder, it tell > me it can't flag messages when all I want to do is read the message, > never said anything about flagging the bloody things.
Stick a pin! Time Out!:) We're both running TB!. We're both using FastMail accounts. Our experiences are like night and day in their difference. You know that I'm not without problems. However, I can be using TB! for mail despite being one who doesn't take well to being hassled excessively. In the end, I just want to read my mail too and that's what I'm currently doing with TB!. I do wonder why we have such contrasting experiences and I do believe it may be a connection issue. Our contrasting experience, makes me remember the days when there were many who wouldn't take to the idea that NAV could be interfering with TB! when it doesn't interfere with other e-mail clients and never interfered with TB! for years. The same can be said for Zone Alarm. Many who had problems with it and TB!, *including myself*, were resistant to entertaining ZA as being the problem because it didn't affect other e-mail clients and that TB! worked for a long time with it. However, with these experiences, we know all too well, that our machines aren't static and that what wasn't a problem before can become a problem, and a problem that affects one application cannot be dismissed as being caused by factor A, simply because the same factor A doesn't affect similar applications. Our difference in experience forces me to think along these lines, in that there's a factor at work here. One that Mulberry is immune to. Initially, I thought it was a difference in TB! configuration. However, it seems not to be. So I have to think along the lines of the connection. Now, I'm not saying that your machine is ailing, while TB! is OK. Not at all. However, there's something about your machine's setup and its connection to your ISP that may be interfering with how TB! does its thing with the IMAP server, while Mulberry isn't bothered. Let me give you an example. When I started using Mulberry, incessant crashing on sending messages had me throwing it aside in haste. When TB! got worse, I revisited Mulberry and took days on end trying to figure out why the darn thing crashed so much. What had me thinking that it was something specific to my system was that Gary did not have the crashes and he was using the same Mulberry version with the same IMAP server. After much searching, I discovered that it was a server setting that was causing it. Once I disabled the setting, all was fine. Of course, Gary didn't have that setting enabled on his server. During all of this, TB! had no problems whatever sending mail, and it still doesn't. Your problems certainly make for food for thought. The question is how to debug the problem. Your debug logs are likely where the questions will be answered. -- -= Allie M.=- Using TB! v3.51 System Specs: http://specs.aimlink.name =-=-= ...The pendulum has gone full circle. ________________________________________________________ Current beta is 3.51 | '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/
