From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.devel Subject: Re: imap process not running Date: Wed, 16 Feb 2005 18:13:42 +0100 Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1108575713 1759 80.91.229.2 (16 Feb 2005 17:41:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 16 Feb 2005 17:41:53 +0000 (UTC) Cc: bugs@gnus.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 16 18:41:53 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D1TBB-00059f-H4 for ged-emacs-devel@m.gmane.org; Wed, 16 Feb 2005 18:41:37 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D1TRA-00064i-8x for ged-emacs-devel@m.gmane.org; Wed, 16 Feb 2005 12:58:08 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D1TQ5-0005ea-7o for emacs-devel@gnu.org; Wed, 16 Feb 2005 12:57:01 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D1TQ2-0005dQ-Qm for emacs-devel@gnu.org; Wed, 16 Feb 2005 12:56:59 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D1TNL-0004ZV-1O for emacs-devel@gnu.org; Wed, 16 Feb 2005 12:54:11 -0500 Original-Received: from [217.13.230.178] (helo=yxa.extundo.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1D1SkT-0001lT-7U for emacs-devel@gnu.org; Wed, 16 Feb 2005 12:14:02 -0500 Original-Received: from latte.josefsson.org (c494102a.s-bi.bostream.se [217.215.27.65]) (authenticated bits=0) by yxa.extundo.com (8.13.2/8.13.2/Debian-1) with ESMTP id j1GHDmGT000674 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 16 Feb 2005 18:13:52 +0100 Original-To: Stefan Monnier OpenPGP: id=B565716F; url=http://josefsson.org/key.txt Mail-Copies-To: nobody X-Hashcash: 1:21:050216:emacs-devel@gnu.org::DQItk6MpQz/OzQB6:14IQ X-Hashcash: 1:21:050216:monnier@iro.umontreal.ca::SB7iU9QrFvpWltWJ:o/5 X-Hashcash: 1:21:050216:bugs@gnus.org::+yBZ9bMbu+vZLBSJ:B7De In-Reply-To: (Stefan Monnier's message of "Mon, 14 Feb 2005 11:53:02 -0500") User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/22.0.50 (gnu/linux) X-Virus-Scanned: ClamAV version 0.81, clamav-milter version 0.81b on yxa.extundo.com X-Virus-Status: Clean X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: main.gmane.org gmane.emacs.devel:33556 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33556 Stefan Monnier writes: > [ I'm using the Emacs-CVS code, running on a GNU/Linux system using an > IMAP/SSL connection using the `openssl' executable. ] > > Every once in a while, Gnus complains that the imap process is not running. > Usually it automatically restarts it behind my back, but occasionally it > burps instead. > > The error I looks like the attached backtrace. > > Debugger entered--Lisp error: (error ) > process-send-string(# "2442 UID FETCH 3355:3364 (UID RFC822.SIZE BODY BODY.PEEK[HEADER.FIELDS (Subject From Date Message-Id References In-Reply-To Xref To Newsgroups)]) It seems a call to process-status could be added to avoid the error. However, Gnus/nnimap is supposed to check whether the server is alive before attempting to use it, and that code call process-status. So a proper solution may be to track down what Gnus/nnimap operation it is that call the backend unconditionally, and fix that, then the server would be automatically re-opened as well. I can try to find to work on adding the process-status call in imap.el, to avoid the error, but depending on error propagation, it may not be sufficient. It will take a while, though, so if you or someone want to look into this, that would be appreciated... You might want to test with GnuTLS instead of OpenSSL too, tls.el might be more reliable. Thanks.