Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!rutgers!husc6!ut-sally!seismo!sundc!hadron!jsdy
From: jsdy@hadron.UUCP (Joseph S. D. Yao)
Newsgroups: net.mail.headers
Subject: Re: CONFIRM: DELIVERY
Message-ID: <591@hadron.UUCP>
Date: Thu, 2-Oct-86 04:36:37 EDT
Article-I.D.: hadron.591
Posted: Thu Oct  2 04:36:37 1986
Date-Received: Sat, 4-Oct-86 12:07:17 EDT
References: <4070@brl-smoke.ARPA>
Reply-To: jsdy@hadron.UUCP (Joseph S. D. Yao)
Organization: Hadron, Inc., Fairfax, VA
Lines: 27
Summary: Return-Receipt-To:, Sen[dt]-Receipt:

In article <4070@brl-smoke.ARPA> Jacob_Palme_QZ%QZCOM.MAILNET@MIT-MULTICS.ARPA writes:
>message has "CONFIRM: DELIVERY" in the RFC822 header, then
>when the message has been delivered to the recipient mailbox,
>a message is sent back to the SMTP-sender saying that this

One hopes you mean the original sender, rather than the last
SMTP link in the route?

You've already had mentioned sendmail's Return-Receipt-To:.
This is supposed to send a receipt when it (sendmail) recieves
the mail at what it thinks is the local delivery machine.
(Sendmail has very definite ideas about "local" -- as someone
pointed out, they MIGHT be right.)  This has seemed to work
in the past.

A certain mail system (user agent) wanted to have instantaneous
receipt on to OR cc OR both, when mail was read.  The attribute
used was Send-Receipt:, which was changed to Sent-Receipt: after
the receipt went back (so that the mail file didn't have to be
re-built, and the header file could be re-built correctly).  The
mail had to be sent out in two calls to sendmail, in case one
wanted receipts from To but not Cc, or vice versa.
It all ... works ...
-- 

	Joe Yao		hadron!jsdy@seismo.{CSS.GOV,ARPA,UUCP}
			jsdy@hadron.COM (not yet domainised)