Gnus development mailing list
 help / color / mirror / Atom feed
From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: on downloading too much data when there's no news
Date: Thu, 06 Aug 2020 21:54:58 +0200	[thread overview]
Message-ID: <87h7tfh7n1.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <878serd0a1.fsf@tullinup.koldfront.dk>

Adam writes:

> But now we are deeper into how Gnus works than what I know :-)

It looks like you can configure Gnus to use GROUP instead of LIST
ACTIVE:

,----[ C-h v nntp-server-list-active-group RET ]
| nntp-server-list-active-group is a variable defined in ‘nntp.el’.
| Its value is nil
| 
| Documentation:
| If nil, then always use GROUP instead of LIST ACTIVE.
| This is usually slower, but on misconfigured servers that don’t
| update their active files often, this can help.
| 
| This is a Gnus server variable.  See Info node ‘(gnus)Select Methods’.
`----

So maybe try something similar to:

        (nntp "fidonet" 
              (nntp-server-list-active-group nil)
              (nntp-address "news.fidonet.fi"))

in your secondary select methods.

For me that helps, ngrep shows this when fetching news, subscribed to
fidonews:

  asjo@tullinup:~$ sudo ngrep -q -Wbyline host news.fidonet.fi
  interface: wlp82s0 (192.168.1.0/255.255.255.0)
  filter: ( host news.fidonet.fi ) and ((ip || ip6) || (vlan && (ip || ip6)))

  T 2a06:4001:d06f:0:909a:cc99:d2b8:3fa6:45732 -> 2001:41d0:401:3100::1030:119 [AP] #1
  GROUP fidonews.


  T 2001:41d0:401:3100::1030:119 -> 2a06:4001:d06f:0:909a:cc99:d2b8:3fa6:45732 [AP] #2
  211 3290 1 3290 fidonews Group selected.


  Best regards,

    Adam

-- 
 "Subdued flamboyance"                                      Adam Sjøgren
                                                       asjo@koldfront.dk



  reply	other threads:[~2020-08-06 19:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 14:13 Wayne Harris
2020-08-06 19:47 ` Adam Sjøgren
2020-08-06 19:54   ` Adam Sjøgren [this message]
2020-08-07  0:39     ` Wayne Harris
2020-08-07  1:07       ` Amin Bandali
2020-08-07  2:45         ` Wayne Harris
2020-08-07 17:40       ` Russ Allbery
2020-08-07 17:44       ` Adam Sjøgren
2020-08-07  0:23   ` Wayne Harris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7tfh7n1.fsf@tullinup.koldfront.dk \
    --to=asjo@koldfront.dk \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).