On Thu, Aug 06, 2015 at 11:30:12PM +0200, Aurélien Rivet wrote: > [2015-08-03 15:02:22] SSL error: I/O error > [2015-08-03 15:02:22] mutt_socket_write: error writing (Connexion > ré-initialisée par le correspondant), closing socket
This message comes from glibc and means "Connection reset by peer" in English. It happens when the server sends TCP reset packet. Reseting TCP is not standard way how to close a TCP connection. It usually happens when a TCP packet with unexpected TCP numbers is received from the client and the server cannot match it to any opened TCP connection. Such a bad packet could appear if previous client's packets were lost, so the bad packet comes (too much) out of order (for example there is a high packet loss on the line), or the server was restarted so it does not know old connections, or the client was resumed from an hybernation and tries to continue in very old already expired connections, or there is some broken firewall inbetween which classify the packet as bad and rejects it, or there is an attempt to hijack the TCP connection by a third party, for example NSA is closer to the Microsoft's server than a client in France, thus the client's packets come after the NSA's were accepted by the server. Or Microsoft is just weired and violetes TCP standards as usual (two-phase TCP hand-shake etc.). Of course this does not explain why Thunderbird works. Maybe my dignostics is wrong and the message comes from different piece of software and has different cause. Or Thunderbird uses different encryption so NSA does not try. Or Thunderbird silently reopens the connection without notifying the user. -- Petr
signature.asc
Description: PGP signature
