Re: [binc] Marking messages as read doesn't work
I had similar problems with outlook, even went as far as tcpdumping the communication.. Unfortunatly, I had to replace binc, as this bug was annoying my client too much. - otherwise I would have been able to look at the problem in more detail. 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. Regards Alan On Mon, 2005-12-12 at 11:02 -0800, Bob Van Zant wrote: I use MS Entourage on OS X to check my email. I have three IMAP accounts that I routinely check. One is on an exchange server, another a Cyrus IMAP server and finally a Binc IMAP server. Every morning I get 4 status emails to my binc server that I quickly read. Entourage marks these messages as read and then a few minutes later it will set the unread count for Inbox to 1. I click on Inbox and wait a few seconds as it figures out that at least one (and sometimes more) of the messages I had just read are now marked unread again. This doesn't happen with any other IMAP server I've ever used with any MUA I've ever played with. I haven't tried to repro this with another MUA on binc simply because I'm lazy. Any ideas? I'm happy to provide more information I just don't necessarily know what is relevant. -Bob
Re: [binc] Marking messages as read doesn't work
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.
Re: [binc] Marking messages as read doesn't work
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.
