IETF Logo Mail Archive

Re: header-munging

Tim Goodwin <tim@uunet.pipex.com> Tue, 13 August 1996 12:52 UTC

Received: from ietf.org by ietf.org id aa27355; 13 Aug 96 8:52 EDT
Received: from cnri by ietf.org id aa27351; 13 Aug 96 8:52 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa05626; 13 Aug 96 8:52 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id IAA29010; Tue, 13 Aug 1996 08:19:59 -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 IAA28997 for <ietf-smtp@list.cren.net>; Tue, 13 Aug 1996 08:19:42 -0400
Received: (qmail-queue invoked from smtpd); 13 Aug 1996 12:19:37 -0000
Received: from pool.pipex.net (158.43.134.17) by pool.pipex.net with SMTP; 13 Aug 1996 12:19:37 -0000
Message-Id: <AAAvTjIQctgADsRv@pipe.pipex.net>
Date: Tue, 13 Aug 1996 13:19:36 +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 mailing list <ietf-smtp@list.cren.net>
Subject: Re: header-munging
In-Reply-To: <EJOM144793694B@MPA15AB>
X-Listprocessor-Version: 8.0 -- ListProcessor(tm) by CREN

> It might be a good idea to extend SUBMIT so that the client can say
> either SUBMIT or RELAY.  If the client says RELAY, that tells the MTA
> not to muck with the message at all (except of course to add a received
> header).

So now every sender-SMTP that wants its messages relayed intact must: i)
use ESMTP; ii) check the supported extensions to see if SUBMIT is among
them; and iii) if it is, send RELAY with the MAIL command.

This seems like a significant step in the wrong direction.

Tim.

v2.23.0 | Report a Bug | By Email