From: John Moreno <phenix@interpath.com>
Cc: "Karl-Johan Noren" <k-j-nore@dsv.su.se>
Subject: Re: GNKSA and Gnus
Date: Mon, 5 Jan 98 16:22:04 -0500 [thread overview]
Message-ID: <199801052121.QAA10293@mail.interpath.net> (raw)
Russ Allbery wrote:
>Per Abrahamsen <abraham@dina.kvl.dk> writes:
>
>> I often have to manually edit the references line when posting followups
>> in gnu.misc.discuss in order to make INN accept it. I guess it happens
>> in gnu.misc.discuss because
>
>> 1) The threads there are very deep.
>> 2) There are a high fraction of Gnus users, thus none of the posters
>> software will restrict the header.
>
>I stand corrected.
>
>> ## Maximum size of a single header.
>> #### =()<MAXHEADERSIZE @<MAXHEADERSIZE>@>()=
>> MAXHEADERSIZE 1024
>
>I believe this only affects headers which are not continued. If one uses
>continuation lines, headers can be much larger. (Or that at least is my
>understanding.) Keep in mind that the version of Gnus that I'm using
>still wraps References using continuation lines; I think Lars took that
>out at some point?
>
>It sounds like either the header wrapping code needs to be put back in or
>Gnus needs to shorten the Reference headers it generates, in the short
>term. In the long term, I expect the new news RFC to require References
>headers not be truncated.
It's going to have to either require or allow it to be truncated at some
point - otherwise you'll have references lines that grow infinitely long.
I know of several threads that are more than a year old - I hate to
think how long they would be if software didn't truncate the header.
Approximately 1k REALLY is the current expected behavior. And if
newsreaders don't do it, servers and users will. It is also a attempt to
make the standard larger than what might otherwise be settled upon -
after all assuming that all of the articles are there threading can take
place with just one, and if articles are missing keeping only 5 or 6 back
references is enough for normal situations. And I can't count the number
of users (most using TIN) who I've chided for deleting it entirely - I
end up telling them that since they feel they must cut it, to at least
leave in the last reference. Unfortunately I often get the reply that it
is simply easier to cut it all out than to try to edit it.
--
John Moreno
next reply other threads:[~1998-01-05 21:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-05 21:22 John Moreno [this message]
1998-01-05 22:02 ` Lars Balker Rasmussen
[not found] <199712280107.UAA02498@mail.interpath.net>
1998-01-05 19:54 ` Per Abrahamsen
1998-01-05 20:31 ` Russ Allbery
1998-01-12 22:15 ` Lars Magne Ingebrigtsen
1998-01-12 22:45 ` Russ Allbery
1998-02-02 18:25 ` Lars Magne Ingebrigtsen
1998-01-12 22:48 ` Hrvoje Niksic
-- strict thread matches above, loose matches on Subject: below --
1998-01-04 22:04 [John Moreno <phenix@interpath.com>] " John Moreno
1998-01-08 9:14 ` Russ Allbery
1998-01-04 21:45 [John Moreno <phenix@interpath.com>] " Russ Allbery
1998-01-04 22:27 ` John Moreno
1998-01-04 23:58 ` Matt Simmons
1998-01-05 13:42 ` Robert Bihlmeyer
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=199801052121.QAA10293@mail.interpath.net \
--to=phenix@interpath.com \
--cc=k-j-nore@dsv.su.se \
/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).