Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!necntc!ames!oliveb!jerry
From: jerry@oliveb.UUCP (Jerry F Aguirre)
Newsgroups: comp.sources.d,news.misc,news.admin
Subject: Re: Wish list
Message-ID: <1047@oliveb.UUCP>
Date: Wed, 20-May-87 17:29:54 EDT
Article-I.D.: oliveb.1047
Posted: Wed May 20 17:29:54 1987
Date-Received: Sat, 23-May-87 07:50:43 EDT
References: <969@bobkat.UUCP> <419@dasys1.UUCP>
Reply-To: jerry@oliveb.UUCP (Jerry F Aguirre)
Distribution: world
Organization: Olivetti ATC; Cupertino, Ca
Lines: 14
Xref: mnetor comp.sources.d:697 news.misc:416 news.admin:476

In article <419@dasys1.UUCP> rsweeney@dasys1.UUCP (Robert Sweeney) writes:
>How about introducing an item into the message header called a conversation
>code (or something to that effect).  It need not be displayed when you read
>the message - it's for "internal use only."  A code is generated when a
>message is posted that does not refer in any way to a previous message.
>All subsequent followups and such are given the same conversation code. The
>"k" and associated commands would seek out and junk articles bearing the
>same code, rather than using the unreliable subject field.

How about using the message ID and references header lines which already
provide this information.  When a followup article is posted the
"Refferences:" header line contains the message IDs of the parent
articles.  No harder to look for than comparing subjects or a
"conversation code".