Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id TAA26865; Thu, 19 Mar 1998 19:13:49 -0500 (EST) Received: by cs.cs.utk.edu (bulk_mailer v1.9); Thu, 19 Mar 1998 19:13:36 -0500 Received: by CS.UTK.EDU (cf v2.9s-UTK) id TAA26820; Thu, 19 Mar 1998 19:13:34 -0500 (EST) Received: from spot.cs.utk.edu (SPOT.CS.UTK.EDU [128.169.92.189]) by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id TAA26807; Thu, 19 Mar 1998 19:13:30 -0500 (EST) Received: from spot.cs.utk.edu by spot.cs.utk.edu with ESMTP (cf v2.11c-UTK) id TAA10008; Thu, 19 Mar 1998 19:13:29 -0500 (EST) Message-Id: <199803200013.TAA10008@spot.cs.utk.edu> X-URI: http://www.cs.utk.edu/~moore/ From: Keith Moore To: mail-std-list@faerber.muc.de (=?ISO-8859-1?Q?Claus_Andr=E9_F=E4rber?=) cc: drums@cs.utk.edu, moore@cs.utk.edu Subject: List behavior In-reply-to: Your message of "19 Mar 1998 20:11:00 +0100." <6qAhhN5ZcDB@faerber.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Mar 1998 19:13:29 -0500 Sender: moore@cs.utk.edu > Mailing lists, however, are much more like news than "classic" email. As > most destination headers (To) simply get lost when passed to mailing > list exploders, if would be nice to have a new header -- let's call it > Lists -- to indicate the mailing lists (yes, plural -- that's the whole > point of it) where the message has been sent. Huh? Most mailing list exploders don't mung destination headers, and I don't see any need for the standard to make special provisions for those that do. Keith