From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/6963 Path: news.gmane.org!not-for-mail From: "Bruno Hertz" Newsgroups: gmane.emacs.gnus.user Subject: Re: Prevent "LIST ACTIVE group" for specific nntp servers? Date: Fri, 31 Mar 2006 11:41:00 +0200 Organization: hispeed.ch 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 1143801652 454 80.91.229.2 (31 Mar 2006 10:40:52 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 31 Mar 2006 10:40:52 +0000 (UTC) Original-X-From: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Fri Mar 31 12:40:49 2006 Return-path: Envelope-to: gegu-info-gnus-english@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FPH3e-0006Uq-TF for gegu-info-gnus-english@m.gmane.org; Fri, 31 Mar 2006 12:40:47 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FPH3e-0000DR-CP for gegu-info-gnus-english@m.gmane.org; Fri, 31 Mar 2006 05:40:46 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!syros.belnet.be!news.belnet.be!newsfeed00.sul.t-online.de!t-online.de!newsfeed.freenet.de!newsfeed01.chello.at!newsfeed02.chello.at!news.hispeed.ch.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.gnus User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/22.0.50 (gnu/linux) Cancel-Lock: sha1:kDGb+u/+WGxAtsMrc8IuCWmeNBM= Original-X-Complaints-To: abuse@hispeed.ch Original-Lines: 64 Original-NNTP-Posting-Host: 84.73.234.175 (84.73.234.175) Original-NNTP-Posting-Date: Fri, 31 Mar 2006 11:41:00 +0200 Original-X-Trace: e7a83442cf92cf1ec4f0a06051 Original-Xref: shelby.stanford.edu gnu.emacs.gnus:77146 Original-To: info-gnus-english@gnu.org 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:6963 Archived-At: "Bruno Hertz" writes: > Hi folks > > my ISP just moved their news feed, now apparently using Chiparus for > load balancing. As it happens, article numbers now come out wrong when > Gnus issues "LIST ACTIVE group" during updates on that server. I > informed them, but it's not clear yet whether it's a misconfiguration > issue or a bug. > > Anyway, I'd like to prevent LIST ACTIVE for groups on that server and > rather have Gnus step into the group (via GROUP apparently) for > gathering article counts, at least until that issue is fixed. So > anybody knows if and how this can be achieved? > > Thanks a lot, Bruno. OK, fixed this thanks to groups.google.com. To restate the problem, on my server LIST ACTIVE group gives a wrong message range. Example telnet session: # telnet news.myisp.com 119 Trying 192.168.0.100... Connected to news.myisp.com. Escape character is '^]'. 200 news.myisp.com mode reader 200 Sure! list active comp.unix.solaris 215 Active file follows comp.unix.solaris 0000358796 0000350838 y . group comp.unix.solaris 211 6088 351204 359007 comp.unix.solaris quit 205 Exit articles 0, bytes 0, groups 1, posts 0, postbytes 0 Connection closed by foreign host. Here, 'list active comp.unix.solaris' gives a wrong message range of 350838 to 358796, while the 'group' command gives the correct 351204 to 359007 range. Presumably a server misconfiguration. Now, to prevent Gnus from using LIST ACTIVE and rather use GROUP instead, one has to set nntp-server-list-active-group to nil (default is 'try). Since this is a 'server slot variable', as Lars elsewhere states, one should put it into the server definition given in either gnus-select-method or gnus-secondary-select-methods in your .gnus file. E.g. my gnus-secondary-select-methods now contains the following entry (nntp "news.myisp.com" (nntp-server-list-active-group nil)) and this just works. On my other native servers, 'LIST ACTIVE' is still used, and only for that specific server it's turned off. One issue I observed though is that Gnus will use GROUP also on foreign servers with this setting. Up to now, I had several gmane groups just subscribed as foreign groups. So to still use 'LIST ACTIVE' on them, I had to turn gmane native by putting it into my gnus-secondary-select-methods. With this final tweak, everything's fine now. Thanks, Bruno.