Hi Steven, I had a look and we are nearly there, unfortunately the debug file does not contain time/date indication so it is difficult to correlate certain events to the tcpdump stream; I've opened a CR upstream for this.
The tcpdump file is not showing any sign of connection closure, neither on the client side or the server side, probably it is incomplete? Can you try to collect the tcpdump again? this time don't stop it immediately when the tls_socket_write error happens but wait one or two minutes without doing anything on mutt, sometimes tcpdump buffers its output. Additionally it would also be great to have the output of "netstat -na | grep 993" when the problem happens and the same output when you stop the tcpdump stream (1 or 2 minutes after, as I said) Can you also please provide us with your tar.gzipped .mutt directory so I can have a look at your conf (obviously please scramble any sensible data, if any? So, a summary of what I need 1) a tcpdump stream to your imap server stopped after 2 minutes that the problem happens, remember not to do anything with mutt in the meantime 2) two files containing the output of "netstat -na | grep 993", one taken immediately when the problem happens, another one taken when you stop tcpdump 3) the content of your ~/.mutt directory (and your .muttrc if any) Sorry to ask you many things but I want to be extra-sure about what is going on, so we can fix it quickly. Cheers Antonio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
