I wrote: > my provider's POP3S support stopped working. When I set > pop3-debug to t, my Gnus 5.13 gets a nice " trace of POP > session to $HOST":
> | +OK POP3 server ready <$SOMEID@$HOST>^M > | *** Fatal error: A TLS packet with unexpected length was received. > | *** Server has terminated the connection abnormally. > | Process POP exited abnormally with code 1 > How can I capture ideally all dialog, but at least the > commands Gnus sends, totally ideally with some fancy > ">>>"/"<<<" to differentiate between incoming and outgoing > lines so I can bug my tech support? To finish this up: After a tip from Lars, I advised pop3-send-command and replaced the comments with messages (inserts do not work there). The ultimate culprit in this case was that gnutls-cli (2.6.6 installed here) which is used preferably by Gnus can't communicate with the server that disconnects after the first client command (even "QUIT" :-)). I solved this by customizing tls-program to only include openssl which works flawlessly. Tim _______________________________________________ info-gnus-english mailing list [email protected] https://lists.gnu.org/mailman/listinfo/info-gnus-english
