Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id GAA12634; Mon, 1 Jan 1996 06:27:13 -0500
Received: by CS.UTK.EDU (bulk_mailer v1.3); Mon, 1 Jan 1996 06:24:50 -0500
Received: from nameserver.utcc.utk.edu by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id GAA12297; Mon, 1 Jan 1996 06:24:49 -0500
Received: from ester.dsv.su.se by nameserver.utcc.utk.edu (4.1/2.8s-UTK.UTCC)
	id AA11897; Mon, 1 Jan 96 06:20:36 EST
X400-Received: by /PRMD=SUNET/ADMD=_/C=SE/;
	Relayed; 01 Jan 96 12:17:53+0100
Date: 01 Jan 96 12:17:53+0100
From: "Jacob Palme DSV-SU/KTH" <jpalme@dsv.su.se>
Message-Id: <1227571*jpalme@su-kom.dsv.su.se>
References: <0ktKNGK00WBw4J9dIn@andrew.cmu.edu>
To: ietf-drums <drums@cs.utk.edu>
Subject: Re: Header to label lists (was untitled)

> I have heard numerous people claim a need for a header to identify
> that a message has undergone list expansion, but I have yet
> to hear a clear, rational statement of what problem such a header is
> supposed to solve.

(1) Valuable information to the recipient

(2) Can be used in a client to filter messages from certain lists
    in special ways (e.g. to a folder for each list)

(3) Can be used for loop detection of circular list memberships