On Wed, 2 Apr 2008, simon haywood wrote:
With UW imapd, every 2 minutes the client should receive a
* OK Timeout in 28 minutes
message (this will count down).
I'm not getting those messages. That'll be the problem then...
So, to be clear, you are NOT seeing these "Timeout in ## minutes" messages
every 2 minutes?
There are only two possible explanations. Either
(1) the client is failing to read the messages from the server
or
(2) there is some bug in your copy of the server.
Although it is prudent to follow a policy of "never say never", the (2)
possibility is unlikely. A quick test to dismiss it is to run imapd from
the shell while NOT root (make sure that it says "* PREAUTH", not "* OK")
when it starts, give the command "X IDLE" followed by return, then wait 2
minutes. You should see something like:
% imap/imapd/imapd
* PREAUTH ...more stuff...
x idle
+ Waiting for DONE
...two minute wait...
* OK Timeout in 30 minutes
Assuming that test pans out, the problem is probably (1), a client bug.
The messages that you
mention do not appear in either the server's logs or the client's logs.
Should they appear in the server logs?
It's a protocol negotiation, not something that would be in server logs.
But if the client is recording protocol telemetry, it should be there.
Is there a configuration that I need
to set to make IDLE work (could a configuration have been set to prevent
it?).
Nope. By design, UW imapd is largely configuration-free. You have to
edit source code to prevent IDLE.
One last thought... I had assumed that the IDLE "channel" used a
standard IMAP port (eg 143). Is that the case?
Yes. It occurs within the IMAP session. There is no separate "channel".
-- Mark --
http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
