Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id QAA12083; Sun, 15 Dec 1996 16:05:52 -0500 Received: by CS.UTK.EDU (bulk_mailer v1.7); Sun, 15 Dec 1996 16:04:47 -0500 Received: by CS.UTK.EDU (cf v2.9s-UTK) id QAA11896; Sun, 15 Dec 1996 16:04:43 -0500 Received: from koobera.math.uic.edu (qmailr@koobera.math.uic.edu [128.248.178.247]) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id QAA11885; Sun, 15 Dec 1996 16:04:39 -0500 Received: (qmail 10400 invoked by uid 666); 15 Dec 1996 21:10:28 -0000 Date: 15 Dec 1996 21:10:27 -0000 Message-ID: <19961215211027.10399.qmail@koobera.math.uic.edu> From: "D. J. Bernstein" To: drums@cs.utk.edu Subject: Re: blank line as head/body separator > Thus only messages whose first body line happens to start with > some text and a colon, or with white space, will really cause a problem, This is a very good point. My header parser allows header lines that (1) start with space, (2) start with tab, (3) start with "From " (I insert "MBOX-Line: "), or (4) start with one or more 33-126, zero or more 8/32, and a colon. If I see anything else, I insert a blank line and end the header. Keith, could you review your examples of invisible continuation lines? In the cases where they were meant as separators, which header fields would be added by the above rules? Would there actually be any damage? ---Dan Put an end to unauthorized mail relaying. http://pobox.com/~djb/qmail.html