Hi 9Val, On 8/5/2005 12:07 AM +0300, you wrote:
In the IMAP direction I see 3 main problems: 1. TB! hasn't thought as IMAP client when was created (mostly fixed)
I hope so. :)
2. Users sometimes try to use IMAP as they use POP. It is completely wrong and it gives bad results.
Right. However, I've been using IMAP for over a year now and I assure you that I no longer use it as I use POP. I still have issues with it.
Even if all that it can do now works as it should without glitches etc., I'd still not be happy because of the POP legacy very slowly being relinquished.
3. Personally I couldn't reproduce most of the bugs reported. As a programmer you should know how it is to deduce the reason in the air.
I don't know the nature of your test environment, but perhaps the problem starts there.
I do very little filtering using TB! and there are those who are doing all filtering with TB!. They'll likely have a lot of problems that I won't because I don't filter much with TB!.
Gary works mainly from his Inbox and then filters after reading. His Inbox is quite busy while reading. It wasn't until I had a lot of messages coming into TBBETA during a test session that I began to experience problems he did and up to then couldn't reproduce.
I'm working with IMAP folders that commonly contain thousands of messages, my largest containing 12,000 messages with a tbi file size of 6.6MB. While using it I got a cascade of AV's. Mind you things seemed smooth for a while. When I restarted TB! and tried accessing the mailbox, TB! offered to repair the mailbox it had problems accessing. I need to delete the cache there.
IOW's, environments largely differ from server to server and the way we use TB! IMAP. Both seem to affect operations quite a lot.
Another thing I need to ask is why offer ways of using TB! IMAP that amount to crippling it. I don't understand that. Why complain that they're using options that *are provided*. It's not intuitive to see full synchronization as an option and then leave everything to not synchronize. It seems unworkable to the passing user. I have found myself having to suggest ways of using TB! and assuring the user that it should work better. In other words, 'It may seem strange to set things up like that, but that's how it works best.' Don't use any of those 'nice' options. :)
Mulberry and ThunderBird present themselves in a simpler way. The out of the box behaviour just works and they will not do some of the things TB! will. They don't need to. A low bandwidth connection cannot handle some of those off-line use type options, and yet a high bandwidth connection doesn't need them though they can handle them.
-- Allie Martin System specs: http://www.ac-martin.com/sysspecs.htm -=-=- IBM: I Buy Macinstosh
________________________________________________________ Current beta is 3.5 Return RC/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/
