> From: owner-openssl-us...@openssl.org On Behalf Of Dr. Stephen Henson > Sent: Tuesday, 19 February, 2013 07:20
> On Tue, Feb 19, 2013, Eisenacher, Patrick wrote: > Aside: the original of that message shows as empty (no text) in my Outlook. I can look at headers and they seem reasonable (text/plain utf8, base64) although Content-Language: is de-DE and the quoted content clearly is English. Mr Eisenbacher's message of Mon, 18 Feb 2013 12:04:08 +0100 also shows empty to me but was (seen and) quoted by Mr Bion. I don't know why. > > Additionally, try invoke s_client with the -trace and > -state options to get > > more human readable output. But as Dave has already pointed > out, your > > client's write to the socket fails, because the underlying > connection was > > closed down and you should enable maximum lovlevel in your > server and check > > its logfile for any hints. > > > Small correction: OP's client *read* from socket returned EOF, which here is a failure (not for some other protocols). TCP socket *write* doesn't fail immediately if remote closes; it takes at least one real send to provoke RST, or usually quite a bit longer for retries to exhaust. <snip rest> ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
