Hi Wolfgang,
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.
As the CAPABILITIES command has been added in RFC 3977 which defines
Version 2 of NNTP, my guess is that a news client which uses that
command has been updated to conform with RFC 3977.
Of course, that may not be true but such a client would then not be
compliant with servers which are supposed to followed this MUST...
The first 7 lines [of the LIST OVERVIEW.FMT response] MUST (except
for the case of letters) be exactly as follows:
Subject:
From:
Date:
Message-ID:
References:
:bytes
:lines
For compatibility with existing implementations, the last two lines
MAY instead be:
Bytes:
Lines:
even though they refer to metadata, not headers.
The MAY is there so that servers could comply with both RFC 3977 and
clients pre-dating RFC 3977. That's why I suggested that heuristics.
Clients which have implemented RFC 3977 /normally/ shouldn't choke on
receiving ":bytes"...
I should really have ensured CAPABILITIES has previously been sent
before changing the syntax in INN 2.8.0; that's a genuine bug.
slrn currently implements RFC 977 and RFC 2980, corresponding to Version
1 of NNTP, according to the error message it gives:
OVERVIEW.FMT not RFC 2980 compliant -- XOVER support disabled.
It couldn't be said when RFC 3977 is implemented...
--
Julien ÉLIE
« Campagne électorale : c'est l'art de gagner les voix des pauvres avec
l'argent des riches en promettant à chacun des deux de les protéger
contre l'autre. » (Oscar Ameringer)
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)