home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.mail.headers
- Path: sparky!uunet!wupost!sdd.hp.com!network.ucsd.edu!qualcom.qualcomm.com!dorner.slip.uiuc.edu!user
- From: sdorner@qualcomm.com (Steve Dorner)
- Subject: Re: Return-Receipt-To & Mailing lists
- Message-ID: <sdorner-291292070904@dorner.slip.uiuc.edu>
- Followup-To: comp.mail.headers,comp.mail.misc
- Sender: news@qualcomm.com
- Nntp-Posting-Host: dorner.slip.uiuc.edu
- Organization: Qualcomm, Inc.
- References: <19921225.001@erik.naggum.no> <sdorner-271292095054@0.0.0.0> <Bzzt68.G8z@boulder.parcplace.com> <1992Dec29.075730.21796@lynx.dac.northeastern.edu>
- Date: Tue, 29 Dec 1992 13:13:49 GMT
- Lines: 19
-
- In article <1992Dec29.075730.21796@lynx.dac.northeastern.edu>,
- tmetro@lynx.dac.northeastern.edu (Thomas Metro) wrote:
- > What should happen when crossing a gateway, and there is no equivalent to
- > a "Return-Receipt-To:" or "Read-Receipt-To:" on the other side? Should the
- > gateway send an appropriate message?
-
- That depends. If the gateway *knows* that the mail is never leaving the
- receipt-less system, then perhaps it might.
-
- "Your mail was delivered to Blackholes 'R Us, which does not support
- return receipts."
-
- However, if there is a significant chance that the mail will emerge from
- the other end (via a .forward kind of mechanism or something), then I would
- think not.
-
- Given my 'druthers, I'd leave this behavior unspecified.
- --
- Steve Dorner, Qualcomm, Inc.
-