On Wed, 11 May 2005, Jonas Mixter wrote: > On 2005-05-10 18:56, Andreas Aardal Hanssen wrote: >> It's a known problem, and a bug in Outlook. If you try Outlook from the >> latest Office packages I believe that this bug has been fixed. It's indeed >> a protocol error from Outlook/Outlook Express, and not a Binc IMAP bug. > So Outlook/Outlook Express uses IDLE mode, which is not supportet by binc, and > fails to see that binc does not support it? Is that correct? > I think I read that the next version of binc should support idle-mode. What is > the status of the development?
No, the mentioned clients support IDLE but the bug still exists there. In short, Binc IMAP times out after 30 minutes of no activity from the client, and Outlook and OE don't expect this. Sometimes they also don't bother with reporting this error, so your client silently goes offline and doesn't get any updates. Binc 1.3 already supports IDLE. Outlook and OE enter IDLE state, then sit around for over 30 minutes without doing anything. :-) >> But of course, once that's been said, there are many security problems >> with using older Outlook and Outlook Express, so there could also be >> the option of looking at alternative clients. > I agree, but unforntunatly I cannot demand that my customers use > specific programs or versions. I could just recommend... True. Thankfully, Binc IMAP is not controlled by any commercial interests, so it can respect the RFC without having to work around broken client behavior. It's really too bad that older Outlook clients have this bug in them, but thankfully I believe it has been fixed in later versions. Andy :-) -- Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg Author of Binc IMAP | "It is better not to do something http://www.bincimap.org/ | than to do it poorly."
