From: Russ Allbery <eagle@eyrie.org>
To: ding@gnus.org
Subject: Re: on downloading too much data when there's no news
Date: Fri, 07 Aug 2020 10:40:21 -0700 [thread overview]
Message-ID: <87h7te8id6.fsf@hope.eyrie.org> (raw)
In-Reply-To: <868sermgqb.fsf@protonmail.com> (Wayne Harris's message of "Thu, 06 Aug 2020 21:39:40 -0300")
Wayne Harris <wharris1@protonmail.com> writes:
> Now, I'm looking at
> https://tools.ietf.org/html/rfc3977#section-7.6.3
> and it seems news.fidonet.net is not violating it. The server does not
> seem to advertise the READER capability. I'm not sure how to see all
> capabilities. I suppose news.fidonet.fi just advertises what it says
> when we connect and that's it.
news.fidonet.fi doesn't support the CAPABILITIES command, so it's not in
compliance with RFC 3977. It may predate the RFC, or it may not intend to
comply. It's some NNTP implementation with which I was not previously
familiar:
200 Welcome to SmapiNNTPd/Linux/IPv6 1.3 (posting may be allowed)
It appears to be specific to file formats used by BBS systems and was
originally written in 2003, which does indeed predate RFC 3977.
https://github.com/ftnapps/smapinntpd
That LIST ACTIVE behavior is unusual. I've not seen it before. It
doesn't comply with RFC 2980 either, which documents existing practice
prior to RFC 3977. It looks like it's ignoring the ACTIVE keyword and
just returning an RFC 977 response to the LIST command, which is
consistent with the HELP output showing that the author appears to be
focused on RFC 977.
--
Russ Allbery (eagle@eyrie.org) <https://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2020-08-07 17:41 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
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 [this message]
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=87h7te8id6.fsf@hope.eyrie.org \
--to=eagle@eyrie.org \
--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).