Re: Delivery Notifications in SMTP

John C Klensin <KLENSIN@infoods.mit.edu> Tue, 05 October 1993 05:19 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19762; 5 Oct 93 1:19 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa19758; 5 Oct 93 1:19 EDT
Received: from mhs-relay.cs.wisc.edu by CNRI.Reston.VA.US id aa06432; 5 Oct 93 1:19 EDT
Received: from cs.wisc.edu by mhs-relay.cs.wisc.edu with SMTP (PP) id <21238-0@mhs-relay.cs.wisc.edu>; Tue, 5 Oct 1993 00:02:16 +0000
Received: from INFOODS.MIT.EDU by cs.wisc.edu; Tue, 5 Oct 93 00:02:02 -0500
Received: from INFOODS.UNU.EDU by INFOODS.UNU.EDU (PMDF V4.2-13 #2603) id <01H3QEN703QO000CEC@INFOODS.UNU.EDU>; Tue, 5 Oct 1993 01:00:05 EDT
Date: Tue, 05 Oct 1993 01:00:04 -0400 (EDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: John C Klensin <KLENSIN@infoods.mit.edu>
Subject: Re: Delivery Notifications in SMTP
In-Reply-To: <17539.749750722@glengoyne.isode.com>
To: S.Kille@isode.com
Cc: Erik.Huizer@surfnet.nl, ietf-osi-x400ops@cs.wisc.edu, dcrocker@mordor.stanford.edu
Message-Id: <749797204.703726.KLENSIN@INFOODS.UNU.EDU>
X-Envelope-To: ietf-osi-x400ops@CS.WISC.EDU
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Mail-System-Version: <MultiNet-MM(330)+TOPSLIB(156)+PMDF(4.2)@INFOODS.UNU.EDU>

Steve,

Either I'm not understanding part of the issue here, or we have a
rather basic misunderstanding about what is possible (maybe two).  Let's
hope it is the first.

>The DR mapping in 1327 has two objectives to achieve.  
>
>1) Present the user information to the end RFC 822 user.
>
>2) Ensure that key diagnostic information is not lost.   Throwing away
>information in the mapping is very very bad news.   Some fields are
>often so much cruft, but sometimes the information is key to
>disgnosing a problem.

Ok, seems reasonable.   But the mechanism used seems to involve what, to
822, are comment fields.  There is no 822 requirement that comment
fields be displayed to the user.  There is no requirement that they be
available to the user.  There is not even any requirement that they be
retained outside the sending system: a gateway, or UA-level relay, can
arguably simply discard them and still be in spec.

That is a pretty poor facility on which to rely for something you
consider important.

>I think that unless the new 822 format is designed with gatewaying in
>mind, it is unlikely that an upgraded 1327 would be able to use it
>effectively.

Anything one puts in an 822 header at this point is no better than
advisory--even if the information is retained, a receiving system is
free to ignore it (and still claim conformance to 822).  MIME doesn't
change that, although it may change some of the social dynamic over
time.  Consequently, if you really want DRs, you are going to need to
appeal to the transport layer, where  sender can insist that the
receiver acknowledge support for that capability (see Keith Moore's
recent I-D for one such model).  

IMHO, one of the difficulties with 1327 (and predecessors) is that it
collapsed both MTA and MUA (P11/P33) functions onto 822.   Since
competent "pure" 821/822 MTAs don't look at that information, anything
that involves transport or delivery-to-mailbox functionality is going to
get lost or screwed up all too often.

    john