From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/58990 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: Re: possible imap.el bug Date: Tue, 26 Oct 2004 17:54:13 +0200 Sender: ding-owner@lists.math.uh.edu Message-ID: References: <4nwtxtf84q.fsf@lifelogs.com> <4nfz4gc99o.fsf@lifelogs.com> <4nzn2napoz.fsf@lifelogs.com> <4n7jpranuj.fsf@lifelogs.com> <4nsm8f956n.fsf@lifelogs.com> <4nsm8fcr00.fsf@bwh.harvard.edu> <4nvfd7ubzv.fsf@lifelogs.com> <4nr7nmipee.fsf@bwh.harvard.edu> <4n3c01sen4.fsf@lifelogs.com> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1098806190 11352 80.91.229.6 (26 Oct 2004 15:56:30 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 26 Oct 2004 15:56:30 +0000 (UTC) Original-X-From: ding-owner+M7532@lists.math.uh.edu Tue Oct 26 17:56:10 2004 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13] ident=mail) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CMTg9-0001kX-00 for ; Tue, 26 Oct 2004 17:56:10 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu ident=lists) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1CMTg0-00015p-00; Tue, 26 Oct 2004 10:56:00 -0500 Original-Received: from util2.math.uh.edu ([129.7.128.23]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1CMTfv-00015k-00 for ding@lists.math.uh.edu; Tue, 26 Oct 2004 10:55:55 -0500 Original-Received: from justine.libertine.org ([66.139.78.221] ident=postfix) by util2.math.uh.edu with esmtp (Exim 4.30) id 1CMTfm-0003eA-3V for ding@lists.math.uh.edu; Tue, 26 Oct 2004 10:55:46 -0500 Original-Received: from yxa.extundo.com (178.230.13.217.in-addr.dgcsystems.net [217.13.230.178]) by justine.libertine.org (Postfix) with ESMTP id 6D0273A0208 for ; Tue, 26 Oct 2004 10:55:40 -0500 (CDT) Original-Received: from latte.josefsson.org (c494102a.s-bi.bostream.se [217.215.27.65]) (authenticated bits=0) by yxa.extundo.com (8.13.1/8.13.1/Debian-15) with ESMTP id i9QFsZIb022964 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK) for ; Tue, 26 Oct 2004 17:55:36 +0200 Original-To: "Ding Mailing List " X-Hashcash: 1:22:041026:ding@gnus.org::98b5a1175a402218:3d0395 In-Reply-To: <4n3c01sen4.fsf@lifelogs.com> (Ted Zlatanov's message of "26 Oct 2004 11:06:07 -0400") User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux) X-Virus-Scanned: clamd / ClamAV version 0.75-1, clamav-milter version 0.75c on yxa-iv X-Virus-Status: Clean Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:58990 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:58990 "Ted Zlatanov" writes: > On Mon, 25 Oct 2004, jas@extundo.com wrote: > >> It looks fine. I wonder why it hasn't been discovered before. >> Perhaps it actually will solve other hard-to-debug bug reports. > > I still get the wrong buffer associated with a server, it just doesn't > happen many times now. I suspect this line: > > (if (not (imap-open nnimap-address nnimap-server-port nnimap-stream > nnimap-authenticator nnimap-server-buffer)) > > in nnimap-open-connection. I have seen a new problem: when I open a server, it is immediately denied, but if I try to open it again, it works fine, and it appears to be re-using the server buffer created by the first server open. Maybe some return value was accidentally changed to nil by your patch, somehow? Requiring two server open attempts is annoying; if I compose a long message and the IMAP server kick me out, then the GCC fail. > Does imap-open have to take a buffer argument? If not, it will create a new unique one. I think it is better to name the server " *nnimap* foo", to mimic how nntp do things. > I would make it always create the buffer, to be safe, and because > reusing the old buffer has no obvious (to me) benefit. Passwords, stream preferences, and possibly more useful data, are stored in the buffer. Those can be costly to discover again. Especially since IMAP servers typically throw you out after 30 minutes. > At some point, it's called with nnimap-server-buffer set to the > wrong buffer but I don't know where. I do know it happens when many > articles are moved sequentially between IMAP servers. Maybe the problem is in gnus-move.el? > I'll keep investigating, but if we can eliminate the buffer argument > to imap-open I think that would make life much easier. Perhaps you could modify your local copy, temporarily? If some code is using the wrong buffer, perhaps renaming it will somehow trigger the bug more easily.