Article View: comp.mail.misc
Article #1006Re: return receipt
From: Edward Vielmetti
Date: Sat, 29 Aug 1992 02:59
Date: Sat, 29 Aug 1992 02:59
24 lines
1364 bytes
1364 bytes
--next-part
return receipt requested seems like a simple application for MIME. add a
body part with appropriate semantics and put support in your MUA to
generate and receive things proper. then haggle over it at IETF meetings
over fine wines and good company.
--next-part
Content-type: application/x-return-receipt-requested
Please let me know that you've gotten this message. Thanks.
--next-part
I suppose you could embellish it so that the return-receipt part had all
of the necessary info to generate the message (a reply-to= field, let's say)
but that's overkill. The only hassle is to make is as un-ugly as possible
so that people who haven't been MIMEd don't get upset.
Edward Vielmetti, vice president for research, Msen Inc. emv@Msen.com
Msen Inc., 628 Brooks, Ann Arbor MI 48103 +1 313 998 4562
--next-part--
Technical Details
Message-ID:
<17mp7hINN1kn@nigel.msen.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!nigel.msen.com!nigel.msen.com!not-for-mailReferences:
<1992Aug26.152841.18915@sfn.ORG>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!nigel.msen.com!nigel.msen.com!not-for-mail From: emv@msen.com (Edward Vielmetti) Newsgroups: comp.mail.misc Subject: Re: return receipt Date: 28 Aug 1992 22:59:47 -0400 Organization: Msen, Inc. -- Ann Arbor, Michigan Lines: 24 Message-ID: <17mp7hINN1kn@nigel.msen.com> References: <1992Aug26.152841.18915@sfn.ORG> NNTP-Posting-Host: nigel.msen.com Content-type: multipart/mixed; boundary="next-part" X-Newsreader: Tin 1.1 PL3