From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/10312 Path: news.gmane.org!not-for-mail From: David Newsgroups: gmane.emacs.gnus.user Subject: Re: Automatically authenticating at local imap server Date: Tue, 05 Feb 2008 22:58:49 +0100 Message-ID: <874pcncbfq.fsf@arcor.de> References: <87fxw9lr6x.fsf@gaura-nitai.dyndns.org> <87odax2jzi.fsf@member.fsf.org> <874pco7bot.fsf@member.fsf.org> <861w7ruyme.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1202248767 8503 80.91.229.12 (5 Feb 2008 21:59:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 5 Feb 2008 21:59:27 +0000 (UTC) To: info-gnus-english@gnu.org Original-X-From: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Tue Feb 05 22:59:49 2008 Return-path: Envelope-to: gegu-info-gnus-english@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JMVpG-0008Ti-AY for gegu-info-gnus-english@m.gmane.org; Tue, 05 Feb 2008 22:59:34 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JMVoo-00032V-61 for gegu-info-gnus-english@m.gmane.org; Tue, 05 Feb 2008 16:59:06 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JMVom-00031z-DF for info-gnus-english@gnu.org; Tue, 05 Feb 2008 16:59:04 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JMVoj-00030X-Oy for info-gnus-english@gnu.org; Tue, 05 Feb 2008 16:59:03 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JMVoj-00030U-L9 for info-gnus-english@gnu.org; Tue, 05 Feb 2008 16:59:01 -0500 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JMVoj-0006iN-Cv for info-gnus-english@gnu.org; Tue, 05 Feb 2008 16:59:01 -0500 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JMVog-0006Wp-Td for info-gnus-english@gnu.org; Tue, 05 Feb 2008 21:58:58 +0000 Original-Received: from dslb-082-083-043-104.pools.arcor-ip.net ([82.83.43.104]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 Feb 2008 21:58:58 +0000 Original-Received: from de_bb by dslb-082-083-043-104.pools.arcor-ip.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 Feb 2008 21:58:58 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 29 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: dslb-082-083-043-104.pools.arcor-ip.net User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (gnu/linux) Cancel-Lock: sha1:ZKP3rQyvYb+AiWe77KXj8WuRtOg= X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: info-gnus-english@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader \(in English\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Errors-To: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.gnus.user:10312 Archived-At: Ted Zlatanov writes: > D> Jumping to the original message in this group is another problem > D> since we only know the message-id but not the article > D> number. > > You could use the Gnus registry if it's loaded. It will tell you the > last place a message ID was seen (it learns this by looking at the > visible messages every time you enter a group, and by hooking into > spool/move/copy/delete on each backend). Yes, I guess the best way would be to first check the registry for the group and do the additional mairix search only if the registry is not loaded or does not know the location of the message. I don't want to rely solely on the registry though, because of the limitations you describe: > It may not know the location for various reasons, e.g. the user limits > the size of the registry or the message hasn't been seen yet, I guess the latter would be a problem for users with big archive groups which they rarely open. > The registry doesn't currently record the article number, but it could. The article number won't be necessary as Tassilo already mentioned. The lookup through gnus-read-header works just fine. -David