I don't know what this error means. Just showed up today. I use news.eternal-september.org.
OVERVIEW.FMT not RFC 2980 compliant -- XOVER support disabled.
Is it something to do with slrn or an issue with the news server? I use slrn 1.0.3.
OVERVIEW.FMT not RFC 2980 compliant -- XOVER support disabled.
Is it something to do with slrn or an issue with the news server? I use slrn >> 1.0.3.
This is slrn failing to parse the new OVERVIEW.FMT in INN 2.8.
See Julièn's post from last July in <tc6fmu$2q025$1@news.trigofacile.com>.
I must admit that slrn without XOVER is painfully slow and so I'm reverting to the previous version of INN for now.
From a practical point of view, I wonder what the benefit of the new format is
especially as the articles contain the Bytes: and Lines: headers in the traditional
format.
Disambiguating metadata items computed by the server (:bytes and :lines)
and the real contents of the headers (Bytes: and Lines:). It is for consistency with the use of these strings in other commands.
HDR :bytes <mid>
HDR Bytes <mid>
may not return the same results.
Is slrn 1.0.3 sending CAPABILITIES?
Maybe the best move here is to use the "preferred format" per RFC 3977
with :bytes and :lines advertised in LIST OVERVIEW.FMT only when the
news reader has previously used CAPABILITIES? And we keep Bytes: and
Lines: otherwise.
* Julien ÉLIE wrote:
Maybe the best move here is to use the "preferred format" per RFC 3977
with :bytes and :lines advertised in LIST OVERVIEW.FMT only when the
news reader has previously used CAPABILITIES? And we keep Bytes: and
Lines: otherwise.
I'm not sure of the correlation between clients using CAPABILITIES and clients using LIST OVERVIEW.FMT. In slrn's case it would certainly work.
Is slrn 1.0.3 sending CAPABILITIES?
No.
Maybe the best move here is to use the "preferred format" per RFC 3977
with :bytes and :lines advertised in LIST OVERVIEW.FMT only when the
news reader has previously used CAPABILITIES? And we keep Bytes: and
Lines: otherwise.
I'm not sure of the correlation between clients using CAPABILITIES and clients
using LIST OVERVIEW.FMT. In slrn's case it would certainly work.
Subject:
From:
Date:
Message-ID:
References:
:bytes
:lines
HDR :bytes sends metadata.
HDR Bytes: sends value of header "Bytes".
If I understand well, you are suggesting to send :bytes and :lines (in
LIST OVERVIEW.FMT) after CAPABILITIES was sent otherwise to send Bytes:
and Lines:?
Correct?
"HDR Bytes" without the ending semi-colon for the second form.
Exactly. Otherwise, current slrn version cannot access overview data. A
few other news clients may also not deal with that new syntax introduced
with NNTP version 2.
Wolfgang, the fix is committed for INN 2.8.0. You can re-install this version whenever you want. (If you're using generated snapshots, the 20230318 one will have it.)
* Julien LIE wrote:
Wolfgang, the fix is committed for INN 2.8.0. You can re-install thisThanks. I will try 20230318 then.
version whenever you want. (If you're using generated snapshots, the
20230318 one will have it.)
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 80:02:37 |
Calls: | 6,716 |
Files: | 12,247 |
Messages: | 5,358,007 |