Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id PAA00960; Mon, 24 Aug 1998 15:44:04 -0400 (EDT) Received: by cs.cs.utk.edu (bulk_mailer v1.11); Mon, 24 Aug 1998 15:42:33 -0400 Received: by CS.UTK.EDU (cf v2.9s-UTK) id PAA00885; Mon, 24 Aug 1998 15:42:32 -0400 (EDT) Received: from resnick1.qualcomm.com (resnick1.qualcomm.com [206.139.85.98]) by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id PAA00873; Mon, 24 Aug 1998 15:42:27 -0400 (EDT) Received: from ra5399b-port23.qualcomm.com (129.46.55.131) by resnick1.qualcomm.com with ESMTP (Eudora Internet Mail Server 2.1); Mon, 24 Aug 1998 14:41:21 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: resnick@resnick1.qualcomm.com Message-Id: X-Mailer: Eudora [Macintosh version 4.1a14-8.98] Date: Mon, 24 Aug 1998 13:36:15 -0500 To: From: Pete Resnick Subject: field names List-Unsubscribe: Steve Dorner asked me about section 3.6.8, specifically the allowed characters in field names, ftext. Given the definition of ftext, you could have a field which looks like this: "%$&^*&%$#$#: My silly header field since any printable character except colon and space can appear in a field name. We've just encountered something (not sure if it's a POP server or an SMTP server) which chokes on such field names; in this particular case, it decided that a field name that ended with an underscore was not a header field and pushed it and everything following it down into the body. I'm not sure how widespread this problem is. Should the document say anything about this, up to and including changing the syntax such that generate is something simpler, but the accept grammar is what's currently allowed? pr -- Pete Resnick QUALCOMM Incorporated Work: (217)337-6377 or (619)651-4478 Fax: (217)337-1980 or (619)651-1102