DINH Viet Hoa [EMAIL PROTECTED]
if I (as an IMAP client) have to exit quickly and have an open IMAP
connection, I can't wait around for the IMAP server's responses.
What is the reason for this ?
I can think of four possible reasons right away. There might be more.
1. The user closes the
if I (as an IMAP client) have to exit quickly and have an open IMAP
connection, I can't wait around for the IMAP server's responses.
What is the reason for this ?
I can think of four possible reasons right away. There might be more.
1. The user closes the MUA's window.
I don't
if I (as an IMAP client) have to exit quickly and have an open IMAP
connection, I can't wait around for the IMAP server's responses.
In this case, should I send LOGOUT and immediately close the TCP
connection, or should I just close the TCP connection? I can't quite make
up my mind.
I
I find this a tough question to answer. My inclination is just to close
the connection but I cannot offer much justification for that. One
consideration is that, if you send a LOGOUT and then immediately close the
connection, it seems likely that the server will never see the LOGOUT.
it
I find this a tough question to answer. My inclination is just to close
the connection but I cannot offer much justification for that. One
consideration is that, if you send a LOGOUT and then immediately close the
connection, it seems likely that the server will never see the LOGOUT.
Hi,
I have couple of test users on a system, and I am writing an imap
client. Wu-imap server is invoked through inetd once there is a
connection to imap port.
I want the server not to time out, once imap connection is established
between the client and the server.
Is this possible?
Thanks
If you do not send a LOGOUT and just close the connection:
Depending upon how the operating system fields the event to the server, the
server will see it as a Hangup (SIGINT), Terminated (SIGTERM), or as End
of file on stdin. In my experience, the last is the most common.
If the server logs
On Wed, 9 Oct 2002 11:03:28 -0400, Murat Bicer wrote:
I want the server not to time out, once imap connection is established
between the client and the server.
Your client must send a command at least every 29 minutes. There is a NOOP
command which is suitable for this purpose.
Mark Crispin [EMAIL PROTECTED]
There are worse consequences.
...
The result is that the flag changes are lost.
Good point.
The only excuse for a client not to send a proper LOGOUT is if the client
crashes. The LOGOUT command is in the protocol for a reason, and that reason
was not
On Wed, 09 Oct 2002 11:42:52 -0400, Pete Maclean wrote:
Mark, thank you for setting us straight on this. For me, another question
arises: when a server detects a connection break, should it process any
IMAP commands that it has pending for the session, or should it discard
them? Seems to
FWIW, I raised the point that a revised draft will be received with the
IESG today and said that I wasn't planning an additional last call unless
there are substantive changes. Everyone seemed happy with that.
Thank you. Do I need to do anything to cause the IESG to receive draft 20, or
11 matches
Mail list logo