Re: header-munging

Einar Stefferud <Stef@nma.com> Fri, 13 September 1996 19:49 UTC

Received: from cnri by ietf.org id aa06242; 13 Sep 96 15:49 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa12934; 13 Sep 96 15:49 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id OAA25877; Fri, 13 Sep 1996 14:59:31 -0400
Received: from ics.uci.edu (mmdf@ics.uci.edu [128.195.1.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id OAA25862 for <ietf-smtp@list.cren.net>; Fri, 13 Sep 1996 14:59:23 -0400
Received: from nma.com by q2.ics.uci.edu id aa24946; 13 Sep 96 11:58 PDT
Received: from localhost by odin.nma.com id aa12256; 13 Sep 96 11:53 PDT
Message-Id: <12254.842640833@odin.nma.com>
Date: Fri, 13 Sep 1996 11:53:53 -0700
Reply-To: ietf-smtp@list.cren.net
Sender: owner-ietf-smtp@list.cren.net
Precedence: bulk
From: Einar Stefferud <Stef@nma.com>
To: ietf-smtp@list.cren.net
Subject: Re: header-munging
In-Reply-To: Your message of "Fri, 13 Sep 1996 12:43:07 BST." <AABnKzI5SMsADG5s@pipe.pipex.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <12252.842640832.1@odin.nma.com>
X-Sender: stef@nma.com
X-Listprocessor-Version: 8.0 -- ListProcessor(tm) by CREN

ABSOLUTELY!!!  

>From Tim's message Fri, 13 Sep 1996 12:43:07 +0100:
}
}> The I-D draft-gellens-submit-01.txt proposes an ESMTP keyword to specify
}> RELAY or SUBMIT, and also suggests an optional additional port.
}
}Please, no.  We're not ISO, nor hostage to any prior art.  Let's
}do one or the other, but not both.
}
}Tim.
} 


Compromising by adopted both is "A Really Bad Idea"(TM).  
The problem with such compromises is that they compromise the result!

Also adding additional functions to an old assigned port number
(commonly known as overloading) is "An Equally Bad Idea" (TM).
Especially when the additional funtionality is drawn what has long
been considered part of another functional standard (i.e., RFC822).

Cheers...\Stef