Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id JAA13626; Tue, 2 Jan 1996 09:27:58 -0500 Received: by CS.UTK.EDU (bulk_mailer v1.3); Tue, 2 Jan 1996 09:27:21 -0500 Received: from VM.SE.LSOFT.COM by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id JAA13530; Tue, 2 Jan 1996 09:27:19 -0500 Message-Id: <199601021427.JAA13530@CS.UTK.EDU> Received: from VM.SE.LSOFT.COM by VM.SE.LSOFT.COM (IBM VM SMTP V2R3) with BSMTP id 1001; Tue, 02 Jan 96 09:27:12 EST Received: from VM.SE.LSOFT.COM (NJE origin ERIC@SEARN) by VM.SE.LSOFT.COM (LMail V1.2b/1.8b) with RFC822 id 3570; Tue, 2 Jan 1996 09:27:12 -0500 Date: Tue, 2 Jan 1996 09:24:35 EST From: Eric Thomas Subject: Re: Header to label lists (was untitled) To: jgm+@CMU.EDU, "Eric Norman (MACC)" cc: drums@cs.utk.edu In-Reply-To: Message of Mon, 01 Jan 96 21:48 CDT from "Eric Norman (MACC)" You can identify that a message has been through a mailing list (as opposed to a multi-user alias like your average 'postmaster' address, which isn't really a mailing list) by looking at the Return-Path: field. For a mailing list it will be either owner-xxx, xxx-request or xxx-owner in all but a few very rare cases. This works today and is as widespread as your new tag is ever likely to get. The reason vacation programs don't handle mailing lists well is that they haven't been updated since the day they were first compiled. I don't see how a new header would help. Eric