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
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,
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
