http://bugzilla.spamassassin.org/show_bug.cgi?id=3917
------- Additional Comments From [EMAIL PROTECTED] 2004-11-01 17:44 ------- Subject: Re: SpamC is reporting "failed sanity check" on some messages >From the MS socket documentation: The semantics of closesocket are affected by the socket options SO_LINGER and SO_DONTLINGER as follows (SO_DONTLINGER is enabled by default; SO_LINGER is disabled). If SO_LINGER is set with a zero time-out interval (that is, the LINGER structure members l_onoff is not zero and l_linger is zero), closesocket is not blocked even if queued data has not yet been sent or acknowledged. This is called a hard or abortive close, because the socket's virtual circuit is reset immediately, and any unsent data is lost. Any recv call on the remote side of the circuit will fail with WSAECONNRESET. If SO_LINGER is set with a nonzero time-out interval on a blocking socket, the closesocket call blocks on a blocking socket until the remaining data has been sent or until the time-out expires. This is called a graceful disconnect. If the time-out expires before all data has been sent, the Windows Sockets implementation terminates the connection before closesocket returns. Enabling SO_LINGER with a nonzero time-out interval on a nonblocking socket is not recommended. In this case, the call to closesocket will fail with an error of WSAEWOULDBLOCK if the close operation cannot be completed immediately. If closesocket fails with WSAEWOULDBLOCK the socket handle is still valid, and a disconnect is not initiated. The application must call closesocket again to close the socket. If SO_DONTLINGER is set on a stream socket by setting the l_onoff member of the LINGER structure to zero, the closesocket call will return immediately and does not receive WSAWOULDBLOCK whether the socket is blocking or nonblocking. However, any data queued for transmission will be sent, if possible, before the underlying socket is closed. This is also called a graceful disconnect. In this case, the Windows Sockets provider cannot release the socket and other resources for an arbitrary period, thus affecting applications that expect to use all available sockets. This is the de fault behavior (SO_DONTLINGER is set by default). Note To assure that all data is sent and received on a connection, an application should call shutdown before calling closesocket (see Graceful shutdown, linger options, and socket closure for more information). Also note, an FD_CLOSE network event is not posted after closesocket is called. Here is a summary of closesocket behavior: If SO_DONTLINGER is enabled (the default setting) it always returns immediately—connection is gracefully closed in the background. If SO_LINGER is enabled with a zero time-out: it always returns immediately —connection is reset/terminated. If SO_LINGER is enabled with a nonzero time-out: – with a blocking socket, it blocks until all data sent or time-out expires. – with a nonblocking socket, it returns immediately indicating failure. For additional information please see Graceful shutdown, linger options, and socket closure for more information. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
