Article View: comp.mail.headers
Article #207Re: Return and read receipts (was Re: Return-Receipt-To & forwarding...)
From: Robert Story
Date: Wed, 30 Dec 1992 17:18
Date: Wed, 30 Dec 1992 17:18
44 lines
2620 bytes
2620 bytes
In article <1992Dec30.072811.3737@robohack.UUCP> woods@robohack.UUCP (Greg A. Woods) writes: > In article <1992Dec28.171751.25819@chance.gts.org> john@chance.gts.org (John R MacMillan) writes: > > I apologize for the length, but this is something I feel fairly > > strongly about. Sprinkle liberally with IMHOs. > > Here Here! Thanks John! > > > My position on this is that receipts are only genuinely useful if they > > are guaranteed. Since we can't get this with the loose email net we > > have, it's not useful. > > I'll go even further: they are "dangerous" in the sense that they > provide incomplete information a false sense of security. As John > said later in his article -- "User expectation is perhaps the biggest > problem." User's I know who say they like this feature are > *completely* mislead by it. > > I'll re-iterate too that even if you get a response, then there's no > guarantee the remote reader will be able to respond, since there's no > way to track between the MTA which thinks it performed final delivery, > and the MUA. Personally, I'm *quite* happy to know that the user's "system" got it. It gives a least some degree of assurance (and besides it makes me feel all warm inside!). > If you want to get a message through to someone, the only sure way to > receive confirmation is out-of-band from the original delivery channel. So, no reply then telephone? Of course, if you get the person's voice mail you're in the same pickle ... how about a personal visit (assuming that the person is not on vacation and still works there!???) > How about updating the mail standards to say that such features are > not permitted! :-) Tut, tut! :-/ Doesn't X.400 have a means of verifying receipt? -Robert. -- _________________________________________________________________________ Robert.Story@Elegant.COM Elegant Communications Inc. Tel: +1 416 362 9772 4 King Street West Suite 1101 Fax: +1 416 362 8324 Toronto, Ontario; CANADA M5H 1B6
Technical Details
Message-ID:
<1992Dec30.171844.17197@elegant.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!uunet.ca!canrem!telly!elegant!rstoryReferences:
<sdorner-271292095054@0.0.0.0> <1992Dec28.171751.25819@chance.gts.org> <1992Dec30.072811.3737@robohack.UUCP>Show Full Headers
Complete Article Headers
Newsgroups: comp.mail.headers,comp.mail.misc Path: arc1-ca.pugleaf.net!sparky!uunet!uunet.ca!canrem!telly!elegant!rstory From: rstory@elegant.com (Robert Story) Subject: Re: Return and read receipts (was Re: Return-Receipt-To & forwarding...) Message-ID: <1992Dec30.171844.17197@elegant.com> Date: Wed, 30 Dec 1992 17:18:44 GMT References: <sdorner-271292095054@0.0.0.0> <1992Dec28.171751.25819@chance.gts.org> <1992Dec30.072811.3737@robohack.UUCP> Organization: Elegant Communications Inc. Keywords: delivery receipts Lines: 45