Received: from localhost (daemon@localhost) by cs.utk.edu with SMTP (cf v2.9s-UTK) id NAA15706; Sun, 30 Jul 2000 13:35:33 -0400 (EDT) Received: by cs.utk.edu (bulk_mailer v1.13); Sun, 30 Jul 2000 13:29:48 -0400 Received: by cs.utk.edu (cf v2.9s-UTK) id NAA15294; Sun, 30 Jul 2000 13:29:48 -0400 (EDT) Received: from draco.cus.cam.ac.uk (marvin@localhost) by cs.utk.edu with ESMTP (cf v2.9s-UTK) id NAA15281; Sun, 30 Jul 2000 13:29:45 -0400 (EDT) Received: from draco.cus.cam.ac.uk (131.111.8.18 -> draco.cus.cam.ac.uk) by cs.utk.edu (smtpshim v1.0); Sun, 30 Jul 2000 13:29:46 -0400 Received: from ph10 (helo=localhost) by draco.cus.cam.ac.uk with local-esmtp (Exim 3.16 #3) id 13IwuF-0006ej-00; Sun, 30 Jul 2000 18:29:43 +0100 Date: Sun, 30 Jul 2000 18:29:43 +0100 (BST) From: Philip Hazel To: Kai Henningsen cc: drums@cs.utk.edu Subject: Re: client requests ending \012 In-Reply-To: <7imD-dUmw-B@khms.westfalen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII List-Unsubscribe: On 29 Jul 2000, Kai Henningsen wrote: > That is, whenever you enable non-RFC behaviour, make it depend on an > option that says, for example, break_rfc_allow_linefeed_lineends, and > defaults to off. A number (but not all) of the RFC-breaking features of Exim do indeed work that way, and I certainly agree with the principle. -- Philip Hazel University of Cambridge Computing Service, ph10@cus.cam.ac.uk Cambridge, England. Phone: +44 1223 334714.