Re: [slrn][pan] Moving Along

Blinky the Shark <no.spam@xxxxxxxxxxx> wrote:
Peter J Ross wrote:

In news.software.readers on Fri, 30 Nov 2007 01:59:36 -0800, Blinky
the Shark <no.spam@xxxxxxxxxxx> wrote:


Just got this from another group (than the one the other heads-ups were
from):

<q edited for brevity>

Date: Fri, 30 Nov 2007 09:50:56 +0100
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
Newsgroups: alt.www.webmaster
References: <slrnfkv03q.utv.no.spam@xxxxxxxxxxxxxxxxxxxxxx>
Message-ID: <474fce8d$1_7@xxxxxxxxxxxxxxx>

Blinky the Shark wrote:

...

Hey, Blinky, what's going on with your References? Your last few posts
have come in unthreaded because they lack References in the headers.

</q>

Please remove my name from the membership list of the slrn mafia. I've
moved over to Pan. It's been fun.

There's obviously a bug in the version of slrn you've been using, but
it's fixed in 0.9.9-69. I'm not sure *when* it was fixed; there's been
a lot of recent work on header-folding issues, but I can certainly
reply correctly to the article you tried to reply to, so it's
certainly fixed now.

Anyway, you'll be pleased to learn that Google Gropes is partly to
blame, because of the unnecessarily long MIDs they've started using
recently. This is how your References header should have looked when
folded:

What is the legal limit for MID length?

As Peter hinted at in the part you snipped, the 'limit' for the
"References: " (or "Message-ID: ") part *plus* the MID is the (RFC 2822
[1]) line length limit of 78 characters. 'limit' in scare quotes,
because the SHOULD limit is 78 and the MUST limit is 998, both excluding
the CRLF.

So this is just another thing Google Groups SHOULD not do, but does.

While this is only a SHOULD violation on the GG / sending side, the
problem in slrn is a *bug*, because the RFC also says:

<quote>

implementations are non-conformant to the intent of this specification
(and that of [RFC2821] if they actually cause information to be lost

</quote>

I.e. GG SHOULD not generate such MIDs, but slrn MUST not fail ("cause
information to be lost") on them.

[1] If you support the idea that RFC 2822 also applies to News articles.
.

Relevant Pages

  • Re: Testing My X-face in Slrn
    ... Blinky the Shark wrote: ... I daresay that you were once new to all this. ... having a pretty frustrating time with slrn today, ...
    (news.software.readers)
  • Re: Boy this place is certainly getting flooded ...
    ... Blinky the Shark added these comments in the current discussion du ... jour ... ... I looked at the headers and while the handle looks normal, ...
    (rec.photo.digital)
  • Re: [slrn][pan] Moving Along
    ... On Fri, 30 Nov 2007, Blinky the Shark wrote: ... Blinky the Shark wrote: ... Hey, Blinky, what's going on with your References? ... Please remove my name from the membership list of the slrn mafia. ...
    (news.software.readers)
  • Re: how to kill google on xnews
    ... Somebody claiming to be Blinky the Shark wrote at ... The solution is not to use slrn. ... Ted <fedya at bestweb dot net> ...
    (news.software.readers)
  • Re: Agent 3.0 Released
    ... On 3 Aug 2005 22:25:27 GMT, Blinky the Shark wrote: ... > Can't you see headers with it? ... Prev by Date: ...
    (news.software.readers)