Hi Steven, from the tcpdump is clear that your connection gets an RST (from the server or a firewall in the middle) after a while, this is your dump:
----- 19:26:37.082874 IP 192.168.1.102.32819 > ey-in-f111.google.com.imaps: Flags [.], ack 125685, win 489, options [nop,nop,TS val 77291 ecr 706190838], length 0 19:36:36.511649 IP ey-in-f111.google.com.imaps > 192.168.1.102.32819: Flags [R], seq 566671823, win 0, length 0 ----- the last thing you send is at 19:26, then you get a RST at 19:36 from the IMAP server; if it's a firewall in the middle or IMAP itself that should not happen because your imap_keepalive is set at 10, so every ten seconds mutt should check your mailbox and keep the connection open, unfortunately it does not happen and this is clear from your tcpdump. It would be nice to see a better correlation between your tcpdump and .muttdebug0 but unfortunately this mutt version has no time/date in the debug file, the next one (1.5.20-1) will have it, so we will be able to collect more data. In the meantime I'm waiting on some more info from the submitter, his mutt hangs when a tls_write_error happens and I've asked for a corefile and a tcpdump as well, at this point I can only say that the imap_keepalive setting is not honoured, but tomorrow I will have more info from the submitter and we can write a better bugreport upstream. Thanks for your collaboration Cheers Antonio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
