Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!mcsun!hp4nl!philapd!idcapd!dejong
From: dejong@idca.tds.PHILIPS.nl (Hans de Jong)
Newsgroups: comp.mail.sendmail
Subject: Re: better return-receipt messages
Message-ID: <1466@idcapd.idca.tds.philips.nl>
Date: 14 Jun 91 11:17:13 GMT
References: <1991Jun13.121110.27660@dartvax.dartmouth.edu> <1991Jun13.143702.14063@mp.cs.niu.edu>
Organization: Philips Information Systems, Apeldoorn, The Netherlands
Lines: 23

rickert@mp.cs.niu.edu (Neil Rickert) writes:

>  1.  Users really should not be using 'Return-Receipt-To:'.  It does not
>      answer the problem of concern to most users.  It is mainly
>      useful as a debugging tool for email administrators.  When viewed
>      from this point of view, returning the headers is essential.

What I find to be the real big problem with Return-Receipt-To: is that the
respons messages do only say from which system they originate, but not
for which user the message is generated. When sending mail to a single address
that is no problem, but when sending to more people, the Return-Receipt-To: 
isn't useful. The same holds by the way for error messages returned by 
sendmail. If a user us unknown, it will tell which user was unknown, but when
e.g. the user's program in the .forward crashes, I have found no clue to which
user this message concerns.
Or did I overlook something?

Hans
-- 
-------------------------------------------------------------------------------
- Hans de Jong				Domain: dejong@idca.tds.philips.nl
-					UUCP:   ..!mcsun!philapd!dejong
- Philips Information Systems	        Apeldoorn, The Netherlands