Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id EAA05842; Tue, 19 Sep 1995 04:37:31 -0400 X-Resent-To: drums@CS.UTK.EDU ; Tue, 19 Sep 1995 04:37:30 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from vall.dsv.su.se by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id EAA05835; Tue, 19 Sep 1995 04:37:26 -0400 Received: from ester.dsv.su.se.noname (ester.dsv.su.se [130.237.161.10]) by vall.dsv.su.se (8.6.10/8.6.9) with SMTP id KAA14796 for ; Tue, 19 Sep 1995 10:37:21 +0200 Received: by ester.dsv.su.se.noname (4.1/SMI-4.1) id AA12378; Tue, 19 Sep 95 10:37:19 +0200 Date: Tue, 19 Sep 1995 10:37:18 +0200 (MET DST) From: Jacob Palme To: ietf-drums Subject: "Comments" RFC 822 heading field Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII My experience is that many mail systems strip of "Comments" headers and do not show them to the recipients. Probably because of this, the "Comments" heading field is not very much used. Because of this, I suggest that the new drums document should either recommend that "Comments" headers are not used, or else define much more specifically in which cases such fields should be used. We should of course not remove the field, since that would break existing software, just recommend not to use it. If a sender wants to separate comments from the main part of his/her message, a better way would be to split the message into two MIME content bodies. ------------------------------------------------------------------------ Jacob Palme (Stockholm University and KTH) for more info see URL: http://www.dsv.su.se/~jpalme