Good point. Yes, that would certainly benefit proposals such as Microsoft
and Yahoos.
It would probably need to be augmented with a BDAT that specifieds the
"chunks" that make up the HEADer only, unless the standard is set so that
the first chunk always contains the header.
Anyway, thanks for pointing this out. Its doable and I think Microsoft
should look at promoting it to help their proposal. It makes sense across
the board otherwise, the pressure is put on SMTP vendors to add DATA hooks
or provide "solutions" or methods for a post smtp support, that might be
outside the whelm of the SMTP software.
--
Hector Santos, Santronics Software, Inc.
http://www.santronics.com
----- Original Message -----
From: "John Gardiner Myers" <jgmyers(_at_)proofpoint(_dot_)com>
To: <ietf-mxcomp(_at_)imc(_dot_)org>
Sent: Wednesday, April 07, 2004 2:09 PM
Subject: Re: User experience
Hector Santos wrote:
What your MCEP (Microsoft' Caller ID Email Policy) design is screaming
for
is a split of the DATA command into two parts, HEAD plus BODY.
The existing CHUNKING extension is quite capable of signalling
rejections before the entire body has been sent. There is no need for a
third way to send the message text.