From: Sudish Joseph <sj@eng.mindspring.net>
Subject: Re: filling the References header
Date: 16 May 1997 14:27:24 -0400 [thread overview]
Message-ID: <yviayb9fz303.fsf@atreides.eng.mindspring.net> (raw)
In-Reply-To: Sudish Joseph's message of 15 May 1997 17:54:03 -0400
Sudish Joseph writes:
> be done in such cases -- off the top of my head, the first two msg-ids
> must be preserved and those closest to the end of the list should also
> be preserved.
Since I've already dug up so1036 once today, I might as correct
myslef. Here're the relevant bits:
1036bis> Followup agents SHOULD not shorten References headers. If
1036bis> it is absolutely necessary to shorten the header, as a des-
1036bis> perate last resort, a followup agent MAY do this by deleting
1036bis> some of the message IDs. However, it MUST not delete the
1036bis> first message ID, the last three message IDs (including that
1036bis> of the immediate precursor), or any message ID mentioned in
1036bis> the body of the followup.
1036bis> [...]
1036bis> When a References header is shortened, at least three blanks
1036bis> SHOULD be left between adjacent message IDs at each point
1036bis> where deletions were made. Software preparing new Refer-
1036bis> ences headers SHOULD preserve multiple blanks in older Ref-
1036bis> erences content.
1036bis> NOTE: It's desirable to have some marker of where
1036bis> deletions occurred, but the restricted syntax of
1036bis> the header makes this difficult. Extra white
1036bis> space is not a very good marker, since it may be
1036bis> deleted by software that ill-advisedly rewrites
1036bis> headers, but at least it doesn't break existing
1036bis> software.
See <URL:ftp://zoo.toronto.edu/pub/news.txt.Z>, it's very well written
(gives background and justifications for lots of seemingly weird
decisions), if incomplete.
-Sudish
next prev parent reply other threads:[~1997-05-16 18:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-05-13 23:30 Roderick Schertler
1997-05-14 1:11 ` Hrvoje Niksic
1997-05-14 17:16 ` Roderick Schertler
1997-05-14 21:37 ` Hrvoje Niksic
1997-05-15 5:42 ` Steven L Baur
1997-05-15 20:43 ` Jason L Tibbitts III
1997-05-15 21:52 ` Stainless Steel Rat
1997-05-15 21:54 ` Sudish Joseph
1997-05-16 18:27 ` Sudish Joseph [this message]
1997-05-17 3:51 ` Lars Magne Ingebrigtsen
1997-05-17 7:35 ` Greg Stark
1997-05-19 0:26 ` Lars Magne Ingebrigtsen
1997-05-19 4:18 ` Roderick Schertler
1997-05-20 20:17 ` Lars Magne Ingebrigtsen
1997-05-17 16:14 ` Jason L Tibbitts III
1997-05-19 0:28 ` Lars Magne Ingebrigtsen
[not found] ` <5los45$gjs$1@arthur.rhein-neckar.de>
1997-05-19 6:47 ` Andreas Jaeger
1997-05-20 16:59 ` Jason L Tibbitts III
1997-05-17 5:15 ` David Moore
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=yviayb9fz303.fsf@atreides.eng.mindspring.net \
--to=sj@eng.mindspring.net \
/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).