🚀 go-pugleaf

Pardon my digression, but I doubt I'm the only one noticing this -

Gary Bacchetti <garyb@buffnet.net> writes:

> Followup-To: alt.internet.services,houston.internet.providers,ne.internet.services,sacramento.internet,necus.internet.news,necus.internet.announce,necus.internet.commerce,misc.news.internet.discuss,alt.internet.access,backbone.general,comp.dcom.telecom.te
>
> ch,comp.dcom.frame-relay,di.internet,

Permit me to point out here the text editor you are using is truncating
lines of article headers to 255 bytes.  This looks like you're using one
named pico - if that's the case have your sysadmin change NLINE=256 to
NLINE=8192 (why fool around?) in estruct.c and recompile.

I used the Followup-To line as an example to make another point (below)
but the real damage here is in the References data - when they are hosed
it breaks the threading on newsreaders that do it properly (of which tin,
despite its name being derived from 'threaded Internet newsreader' is not
one, which is why you likely haven't noticed this).

And then the tin newsreader you are using (v1.2 pl2) has another problem
in that whenever it sees a comma in the newsgroups data in an article
which you are following up (and which article does not also contain a
Followup-To line of its own) it copies those data into one and places it
in your article.  This should be taken out - it's in post.c and isn't
very hard to find - simply removing it fixes the problem.

The only reason to use Followup-To is to modify the Newsgroups - that is,
redirecting respones to something other than the newsgroups listed.

Billy Y..