Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id QAA28194; Fri, 9 Apr 1999 16:42:11 -0400 (EDT) Received: by cs.cs.utk.edu (bulk_mailer v1.12); Fri, 9 Apr 1999 16:38:04 -0400 Received: by CS.UTK.EDU (cf v2.9s-UTK) id QAA27873; Fri, 9 Apr 1999 16:38:03 -0400 (EDT) Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168]) by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id QAA27849; Fri, 9 Apr 1999 16:37:55 -0400 (EDT) Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1]) by astro.cs.utk.edu (cf v3.2) with ESMTP id QAA08578; Fri, 9 Apr 1999 16:35:45 -0400 (EDT) Message-Id: <199904092035.QAA08578@astro.cs.utk.edu> X-URI: http://www.cs.utk.edu/~moore/ From: Keith Moore To: Robert Elz cc: Jacob Palme , IETF working group on revision of mail standards Subject: Re: X-headers cause uexpected behavior In-reply-to: Your message of "Fri, 09 Apr 1999 00:54:56 +1000." <18204.923583296@munnari.OZ.AU> Date: Fri, 09 Apr 1999 16:35:45 -0400 Sender: moore@cs.utk.edu List-Unsubscribe: > The alternative is to make it quite clear that X headers should > never be used for anything (and ideally should never be transmitted > eitehr). They're a poor idea, with almost no rational use. Problem is, vendors are going to put their vendor-specific information somewhere. They will either do it in X- headers and leave the rest of the header name space alone, or they will define their own header names which will cause conflicts not only with other vendors, but also with things we want to standardize in the future. But as I told Jacob in private mail, it's too late for DRUMS to say anything about this. We need to get the DRUMS work out the door, and we can't do that by opening up new issues. Keith