I've doubled the timeout to an hour. See what happens I guess. -Bob
On 12/12/05 5:47 PM, "Andreas Aardal Hanssen" <[EMAIL PROTECTED]> wrote: > On Tue, 13 Dec 2005, Alan Knowles wrote: >> I suspect it's the multi-connection way that MS clients work. and not >> all threads in binc being notified of the change of state. > > From what I've heard, it's the good old outlook bug. Binc disconnects on > timeout after 30 minutes, outlook doesn't expect that, and so when you > mark a message as read, it only happens locally and not on the server. > Better yet, outlook doesn't tell Binc after the connection has been opened > again. > > This is brokenness in outlook, but if you use another client, or increase > the idle timeout in bincimap.conf, the problem should go away. I also > think the latest outlooks don't have this problem. > > 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." >
