Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id JAA00499; Wed, 1 Jan 1997 09:07:03 -0500 Received: by CS.UTK.EDU (bulk_mailer v1.7); Wed, 1 Jan 1997 09:06:43 -0500 Received: by CS.UTK.EDU (cf v2.9s-UTK) id JAA00434; Wed, 1 Jan 1997 09:06:42 -0500 Received: from muenster.westfalen.de (root@muenster.westfalen.de [193.174.5.2]) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id JAA00407; Wed, 1 Jan 1997 09:06:27 -0500 Received: from khms.westfalen.de by muenster.westfalen.de via rsmtp with bsmtp id for ; Wed, 1 Jan 1997 15:01:03 +0100 (MET) (Smail-3.2 1996-Jul-4 #1 built 1996-Nov-13) Received: by khms.westfalen.de (CrossPoint v3.11 R/C435); 01 Jan 1997 14:50:44 +0100 Date: 01 Jan 1997 13:53:00 +0100 From: kai@khms.westfalen.de (Kai Henningsen) To: drums@cs.utk.edu Message-ID: <6O2su02UcsB@khms.westfalen.de> In-Reply-To: <6NvF$IojcsB@khms.westfalen.de> Subject: Re: blank line as head/body separator X-Mailer: CrossPoint v3.11 R/C435 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Organization: Organisation? Me?! Are you kidding? X-No-Junk-Mail: I do not want to get *any* junk mail. Comment: Unsolicited commercial mail will incur an US$100 handling fee per received mail. BKnowles@aol.net (Brad Knowles) wrote on 31.12.96 in <961231113957.ZM25478@chrome.office.aol.com>: > Why? If the client is automated, odds are that (in the name of > efficiency) it will probably be written so that it consistently uses > a single case for commands throughout. Why not specify that all > clients must use uppercase (one of only three options, the others > being lowercase and some variety of mixed case)? Wouldn't that > simplify programming a bit? Yes. It would simplify server programming, by relying on the case. That's what we *don't* want, I thought. I don't see how client efficiency or ease of programming could possibly be affected by the exchange of, say, smtp_put('Mail from:'); to smtp_put('MAIL FROM:'); - could you explain that? MfG Kai