Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id QAA28931; Mon, 5 Aug 1996 16:04:27 -0400 Received: by CS.UTK.EDU (bulk_mailer v1.6); Mon, 5 Aug 1996 16:01:17 -0400 Received: from bbmail1.unisys.com (bbmail1.unisys.com [192.63.200.5]) by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id QAA28458; Mon, 5 Aug 1996 16:01:00 -0400 Received: from mvdns1.mv.unisys.com (mvdns1.mv.unisys.com [192.59.253.100]) by bbmail1.unisys.com (8.7.3/8.6.12) with SMTP id UAA25138; Mon, 5 Aug 1996 20:00:37 GMT Received: from MPA15AB.MV.UNISYS.COM by mvdns1.mv.unisys.com (4.1/SMI-4.1-1.8) id AA07635; Mon, 5 Aug 96 20:00:38 GMT Date: Mon, 5 Aug 1996 12:56:50 -0700 (PDT) (19:56 UT) From: "Randall C. Gellens" To: Philip Hazel Cc: Jacob Palme , ietf-drums Subject: Re: header-munging In-Reply-To: Your message of "5 Aug 1996 10:03:48 +0100" References: Message-Id: On 5 Aug 1996 10:03:48 +0100, Philip Hazel wrote: > On Sun, 4 Aug 1996, Jacob Palme wrote: > > > Which other header-munges do commonly occur, and why? attempts to document which types of header munging an MTA may perform, and when. It says that an MTA may alter headers to fix messages which are being submitted, not relayed, through it, and it gives conditions under which a message can be treated as a submission (including an SMTP extension to formalize this). It does need to be updated to add rewriting of 822 headers and 821 forward and reverse paths for CNAME expansion, and also 822 header rewriting for nickname expansion, and related address modifications which Philip mentions. Comments on draft-gellens-smtp-submit-00.txt are appreciated. It suggests using the mailing list. -- |Randall Gellens | randy@mv.unisys.com| |(714) 380-6350 | fax (714)597-8053 can add ,,,,,,,,6350| |Opinions are personal; facts are suspect; I speak only for myself|