Re: header-munging

Tim Goodwin <tim@uunet.pipex.com> Wed, 14 August 1996 11:15 UTC

Received: from ietf.org by ietf.org id aa19291; 14 Aug 96 7:15 EDT
Received: from cnri by ietf.org id aa19287; 14 Aug 96 7:15 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa04813; 14 Aug 96 7:15 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id GAA16259; Wed, 14 Aug 1996 06:44:56 -0400
Received: from pool.pipex.net (pool-eth0.pipex.net [158.43.128.24]) by list.cren.net (8.6.12/8.6.12) with SMTP id GAA16242 for <ietf-smtp@list.cren.net>; Wed, 14 Aug 1996 06:44:42 -0400
Received: (qmail-queue invoked from smtpd); 14 Aug 1996 10:44:42 -0000
Received: from pool.pipex.net (158.43.134.17) by pool.pipex.net with SMTP; 14 Aug 1996 10:44:41 -0000
Message-Id: <AABNGDIRrhgADtyk@pipe.pipex.net>
Date: Wed, 14 Aug 1996 11:44:40 +0100
X-Orig-Sender: owner-ietf-smtp@list.cren.net
Precedence: bulk
Sender: ietf-archive-request@ietf.org
From: Tim Goodwin <tim@uunet.pipex.com>
To: "Randall C. Gellens" <RANDY@mpa15ab.mv.unisys.com>
Cc: ietf smtp list <ietf-smtp@list.cren.net>
Subject: Re: header-munging
In-Reply-To: <EJPN0542AC3462@MPA15AB>
X-Listprocessor-Version: 8.0 -- ListProcessor(tm) by CREN

> It is far too late to argue that SMTP should not be used for submission.

Agreeed.

> All we can do, as I see it, is either (a) accept the status quo and do
> nothing, or (b) try and improve the situation in an efficient way.

I agree, and I agree that we should strive for (b).

Unfortunately, I really, really, can't see the SUBMIT extension helping.
It's just way too complicated for the client.  Nobody's going to
implement it.

I suppose, maybe, if you're a client that already does ESMTP but submits
broken messages, there might be some point in using SUBMIT.  Such
clients are currently a tiny minority.  For other clients, it would be
simpler to generate conforming RFC 822 messages in the first place.

If we truly hope to overcome the inertia of the status quo, we need
something that's trivial to implement on the client side (and preferably
the server side, too, although that's slightly less important).  The
only suggestion I've seen which I think fits the bill is to use SMTP but
on a different port.

I've written this idea up in internet draft form.  I haven't yet
submitted it, but you can retrieve it from

    ftp://ftp.pipex.net/pub/mail/draft-goodwin-smtp-submit-00.txt

Please let me have any comments.

Thanks,

Tim.