Title: Message
Read receipts are a warm fuzzy client-side feature that just doesn't work.  They do not belong in a corporate setting, in my opinion.  False positives generated by the preview pane,  short messages read in the preview pane and deleted prior to the preview pane changing message status to 'read', client side responses to not send a read receipt as capable in Outlook2002, and if you are talking for external use, well then it is a total crap shoot and even a successfully returned 'read receipt' holds little or no legal value.
 
Because I'm too cheap for Watch Your Back, I use this one for my Outlook2000 clients:
 
Read receipts are just more crap on my servers.
 
-----Original Message-----
From: Kopec, David [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 23, 2002 9:42 AM
To: MS-Exchange Admin Issues
Subject: What an issue!

I have a question/issue. Our legal dept. would like "read receipts" for all e-mails sent out, once they have been read by the recipient. This message originates from a web server and is sent with a program like "Sendmail" to virtually to every employee here.  We have set up a mailbox within the Exchange org which is where they would like the read receipts to return to.  They have a script they are using on the app server (see below) that supposedly is set up to send a read receipt but apparently it does not function. I didn't write it and I don't know much about it. It does send a delivery receipt however.
 
In the CDO message object there is a return-receipt-to value to which can be assigned an e-mail address; and this, as far as I understand, should cause read receipt functionality to occur. However, when the web server sends off the message to the recipient, we get back a "delivery successful" notification (which I don't even really want), but then no subsequent "read receipt", even after the message has been opened and closed.
I checked the Internet headers for the message (see bottom of message), and the Return-Receipt-To header is part of the message, but it seems to be acting like a delivery notification instead.
 
1) Am I incorrect on which header should cause the read receipt functionality to work?
 
Or
 
2)  Do I just have the wrong code?  Or am I beating a dead horse?  I was wondering if thereis a correlation in Exchange/Outlook for which Internet Header "maps" to the read receipt flag in the Outlook client (like it seems the Return-Receipt-To: <[EMAIL PROTECTED]> Internet Header "maps" to the Delivery Receipt Requested checkbox in an Outlook message).
 
I did find an article on MSDN that might have something to do with this, assuming I am correct in #1 above. It is:   http://support.microsoft.com/default.aspx?scid=kb;EN-US;q253917
 
If you could help me out on this, I'd really appreciate it.
 
Thanks,
 

David Kopec Electronic Messaging Specialist
 
Technology Services & Solutions
 
 
 
 
Internet Headers (By looking at View==>Options on message sent from Appdev webserver):
 
Received: from appdev (appdev.mfs.com [168.66.12.121]) by carina.mfs.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
 
id 3YSNZY5A; Tue, 16 Jul 2002 11:28:48 -0400
 
Return-Receipt-To: < [EMAIL PROTECTED]>
 
From: < dkopec @mfs.com>
 
To: < dkopec @mfs.com>
 
Subject: Test Email--Please Open
 
Date: Tue, 16 Jul 2002 11:28:48 -0400
 
 
MIME-Version: 1.0
 
Content-Type: multipart/alternative;
 
boundary="----=_NextPart_000_0063_01C22CBB.F3EEB890"
 
X-Mailer: Microsoft CDO for Windows 2000
 
Thread-Index: AcIs3XsAXZwcwr+eQeWVlnFS6dSgng==
 
Content-Class: urn:content-classes:message
 
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
 
This is a multi-part message in MIME format.
 
------=_NextPart_000_0063_01C22CBB.F3EEB890
 
Content-Type: text/plain;
 
charset="iso-8859-1"
 
Content-Transfer-Encoding: 7bit
 
------=_NextPart_000_0063_01C22CBB.F3EEB890
 
Content-Type: text/html;
 
charset="iso-8859-1"
 
Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_0063_01C22CBB.F3EEB890--
 
 

Reply via email to