Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id KAA18211; Tue, 2 Jan 1996 10:30:55 -0500 Received: by CS.UTK.EDU (bulk_mailer v1.3); Tue, 2 Jan 1996 10:30:35 -0500 Received: from a4.jck.com by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id KAA18155; Tue, 2 Jan 1996 10:30:33 -0500 Received: from white-box ("port 2087"@white-box.jck.com) by a4.jck.com (PMDF V5.0-5 #13246) id <0DKK8EK5Z000BN@a4.jck.com>; Tue, 02 Jan 1996 10:30 -0500 (EST) Date: Tue, 02 Jan 1996 10:30:10 -0500 From: John C Klensin Subject: Re: Header to label lists (was untitled) X-Sender: klensin@mail1.reston.mci.net To: Eric Thomas Cc: drums@cs.utk.edu Message-id: <0DKK8EK60000BN@a4.jck.com> MIME-version: 1.0 X-Mailer: Windows Eudora Pro Version 2.1.2 Content-type: text/plain; charset="us-ascii" Content-transfer-encoding: 7BIT At 09:24 1/2/96 -0500, Eric Thomas wrote: >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. I tend to agree with Eric (and Keith and Harald)... (1) The heuristic above is likely to work much better, for a long time if not forever, than inventing a new header and trying to guess whether the new header is absent because * it isn't a list or * the list-generator hasn't been updated to generate that header. (2) This is out of scope for DRUMS john