From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/36595 Path: main.gmane.org!not-for-mail From: Doug Alcorn Newsgroups: gmane.emacs.gnus.general Subject: Re: Tunelling nnimap through ssh shell (Was: nnimap-authinfo-file question) Date: 05 Jun 2001 15:36:35 -0400 Sender: dalcorn@seapine.com Message-ID: <8766eaoh18.fsf@balder.seapine.com> References: <86n17v7pst.fsf@monsterisland.homonculus.net> <87elsyop3w.fsf_-_@balder.seapine.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035172153 9403 80.91.224.250 (21 Oct 2002 03:49:13 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:49:13 +0000 (UTC) Return-Path: Return-Path: Original-Received: (qmail 8890 invoked from network); 5 Jun 2001 19:43:15 -0000 Original-Received: from unknown (HELO seapine.com) (216.23.11.247) by gnus.org with SMTP; 5 Jun 2001 19:43:15 -0000 Original-Received: from balder.seapine.com [192.168.1.251] by seapine.com [127.0.0.1] with SMTP (MDaemon.v3.5.0.R) for ; Tue, 05 Jun 2001 15:40:36 -0400 Original-Received: from balder.seapine.com (localhost [127.0.0.1]) by localhost (8.12.0.Beta7/8.12.0.Beta7/Debian 8.12.0.Beta7-1) with ESMTP id f55JaZKR030708 for ; Tue, 5 Jun 2001 15:36:36 -0400 Original-Received: (from dalcorn@localhost) by balder.seapine.com (8.12.0.Beta7/8.12.0.Beta7/Debian 8.12.0.Beta7-1) id f55JaZil030704; Tue, 5 Jun 2001 15:36:35 -0400 X-Authentication-Warning: balder.seapine.com: dalcorn set sender to doug@lathi.net using -f Original-To: ding@gnus.org X-Face: +GT&`y}rSVHq>&PvSIvtsy^RC6Agyxq)t+25D#'iTroOnA/'pcE$QD*WU1=WLS*OC\0y-kS |k+)w~x writes: > Doug Alcorn writes: > > > Noticing another thread about problems with nnimap connections timeing > > out, would it be possible to have nnimap send a keepalive message to > > the server? > > Gnus should cope with destroyed network connections, it shouldn't > include workarounds to make sure the network connection isn't > destroyed. OK, I'll buy that. > Did this actually cause anything to fail? If so, what? Gnus should > simply re-open the connection, I think. Well, kindof. What happens is that the next operation that requires a connection to the server hangs indefinitely. The good news is taht C-g will interrupt it and re-doing the same operation does cause nnimap to open a new connection. In practice this is highly annoying. When I leave Gnus for a while (in whatever state) and come back I always have to do something, then interrupt it, then do it again. Another point. The warning message or complaint from nnimap doesn't show up in any buffer I can find. " *Message-Log*" has no record of it (even though the message shows up in the minibuffer). " *nnimap*" is empty as is "*Warnings*". I can't find any other buffers that would seem to be related. -- (__) Doug Alcorn (mailto:doug@lathi.net http://www.lathi.net) oo / PGP 02B3 1E26 BCF2 9AAF 93F1 61D7 450C B264 3E63 D543 |_/ If you're a capitalist and you have the best goods and they're free, you don't have to proselytize, you just have to wait.