From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/36542 Path: main.gmane.org!not-for-mail From: Mats Lidell Newsgroups: gmane.emacs.gnus.general Subject: Re: Imap Problem Date: 01 Jun 2001 09:00:09 +0200 Sender: matlid@spip.netinsight.se Message-ID: References: <76y9rdaxai.fsf@newjersey.ppllc.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035172109 9145 80.91.224.250 (21 Oct 2002 03:48:29 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:48:29 +0000 (UTC) Cc: ding@gnus.org Return-Path: Return-Path: Original-Received: (qmail 11061 invoked from network); 1 Jun 2001 07:00:38 -0000 Original-Received: from gw.contactor.se (HELO pm1.contactor.se) (193.15.23.130) by gnus.org with SMTP; 1 Jun 2001 07:00:38 -0000 Original-Received: from spip.netinsight.se.contactor.se (pm1 [193.15.23.1]) by pm1.contactor.se (8.9.3/8.9.1) with ESMTP id JAA00081; Fri, 1 Jun 2001 09:00:09 +0200 (MET DST) Original-To: Jake Colman User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Academic Rigor) Original-Lines: 29 Xref: main.gmane.org gmane.emacs.gnus.general:36542 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:36542 >>>>> Jake wrote: Jake> Does anyone else have this problem and can suggest a solution? Yes! You are not alone ;-) No! No solution ;-( There might be more situations that can lead to this behavior. Such as the imap connection timing out. What I have found useful is to quite often check for new mail and by that avoid the timeout. One other problem, that I have tried to track down, is that nnimap while connecting looks in the wrong buffer for the reply. Now this might sound strange but somehow the current buffer is changed. I have verified this. So nnimap might be looking for the IMAP responce in the *Group* buffer. This happens every time I start gnus in its own window. My workaround is to start with M-x gnus. So I won't get a new window. My guess is that you can get similar problems when imap has timedout and it tries to reconnect. By looking at the nnimap code I can't however figure out how this can ever happen and obviously the code does work for a lot so it is a really hard bug to find. I guess someone who gets this problem must look into it ;-) OK. Someday ... Yours -- %% Mats