Received: from localhost (daemon@localhost) 
        by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id SAA13846; Wed, 18 Mar 1998 18:48:51 -0500 (EST)
Received: by cs.cs.utk.edu (bulk_mailer v1.9); Wed, 18 Mar 1998 18:48:24 -0500
Received:  
        by CS.UTK.EDU (cf v2.9s-UTK)
	id SAA13738; Wed, 18 Mar 1998 18:48:23 -0500 (EST)
Received: from smtp-out.ipost.net (smtp-out.ipost.net [205.245.41.66]) 
        by CS.UTK.EDU with ESMTP (cf v2.9s-UTK)
	id SAA13724; Wed, 18 Mar 1998 18:48:12 -0500 (EST)
Received: from ipost.net ([209.24.48.175]) by smtp-out.ipost.net (1.0.242) for drums@cs.utk.edu; 18 Mar 1998 18:53:16 -0500
Message-ID: <35105CB6.B2EAE4F1@ipost.net>
Date: Wed, 18 Mar 1998 15:45:58 -0800
From: Jutta Degener <jutta@ipost.net>
Organization: IRDG, Inc.
X-Mailer: Mozilla 4.03 [en] (WinNT; I)
MIME-Version: 1.0
To: drums@cs.utk.edu
Subject: Re: Small Clarification to msg-fmt-04
References: <v04010d0bb134fff777a5@resnick2.qualcomm.com> <v04010d00b135ff9bebf7@resnick2.qualcomm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Pete Resnick wrote:
> I seem to remember (and I don't have
> time to check the archives right now) that there was a good deal of push
> that messages *could* be terminated without CRLF.

Was that RFC 822 or 821?  RFC822 messages without terminating <CRLF> can
make sense, even if they're not deliverable using DATA.  They could be in
a message/rfc822 MIME part, or exchanged using the CHUNKING extension's
BDAT command, or never pass through ESMTP at all.

Jutta Degener
<jutta@ipost.net>