Andreas Aardal Hanssen wrote:
<snip>

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.

If you want to work around the problem, you can increase the idle timeout to some very high value, around the period that you can guarantee that users will access their account with their email client.

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.


For the joke (?), I mean bincimap is a SERIOUS project, respecting all the RFC. You MUST trash Outlook 2000/2003 there respects nothing...
;-)
Francois
FMC Luxembourg

Reply via email to