On Thu, 27 May 2004 12:23:56 -0400, Joseph <[EMAIL PROTECTED]> wrote:

The strange thing is, I don't see anything unusual in the
logs.
The client just times out.

What about the /etc/bincimapd.conf file?
There are two settings in there to do with timing.

Does this need adjusting?


idle timeout = 1860
===================
Server times out if there has been no communication from the clien for 1860 seconds (31 minutes). Most clients poll the server every few of minutes (frequently 5 or 10) to check for new mail. Most clients simply reconnect if the original connection has been dropped (e.g. because the network cable was disconnected). Note that some IMAP clients don't follow protocol properly when this happens (e.g. Opera) and Binc IMAP v1.7final has a bug that prevents the two parties from getting resychronized: see http://www.bincimap.andreas.hanssen.name/archive/?0::1150 for a patch to address this situation. But, I don't know if that is what happens with Outlook. I am running Outlook in my lab right now to see if I can reproduce the problem. Since I have not seen your problem, any ideas on what I can do to reproduce the problem?


auth timeout = 60
=================
Similar to the "idle timeout" but specifically for the authentication stage. Hopefully this helps in the case of a denial of service (DOS) attack. I doubt this is a problem for you.


transfer timeout = 1200
=======================
I am not sure what this time out does.  Andy?

Henry :-)


I will do a protocol dump if that helps or at least
try to do one :)

Thanks.
On Thu, 2004-05-27 at 12:11, Henry Baragar wrote:
On Thu, 27 May 2004 10:47:41 -0400, Joseph <[EMAIL PROTECTED]> wrote:

> We have a lot of problem with the binc 1.2.7final working
> right with Outlook 2002.
>
> It look seems to timeout constantly.
>
> What do you think it would take to fix this?
>
Since this is the first time that this problem has been reported here, we
don't know.


It would help if you could post an URL to your logs with some indication
as to which sessions were timing out.

It would also help if you could do a protocol dump (ala
http://lifewithbincimap.org/index.php/Main/ProtocolDumping) and indicate
the problem sessions.

Henry :-)



-- Henry Baragar Instantiated Software Inc. http://www.instantiated.ca

Reply via email to