Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ll-xn!nike!sri-spam!gds
From: gds@sri-spam.ARPA (The lost Bostonian)
Newsgroups: net.mail.headers
Subject: Re: CONFIRM: DELIVERY
Message-ID: <7329@sri-spam.ARPA>
Date: Wed, 24-Sep-86 20:37:46 EDT
Article-I.D.: sri-spam.7329
Posted: Wed Sep 24 20:37:46 1986
Date-Received: Thu, 25-Sep-86 00:40:33 EDT
References: <4070@brl-smoke.ARPA> <20884@styx.UUCP>
Distribution: net
Organization: the Bay Area, for now
Lines: 15

In article <20884@styx.UUCP>, mcb@styx.UUCP (Michael C. Berch) writes:
> A large percentage of Internet mailers (and at least one user agent) 
> respond to the header field
> 
> 	Return-Receipt-To: <addr-spec>
> 
> confirming delivery of a message to a mailbox (in the case of a
> delivery agent) or reading of the message (in the case of a user
> agent). It isn't in RFC822, but I'd call it a de facto standard among
> 822-style mailers.

Doesn't Return-Receipt-To: cause a mail loop with sendmail?  I seem to
recall having that problem the one time I tried using this feature.

--gregbo