VanguardLH said:
What happens when you define a rule to handle those e-mails that are
read receipts that you requested the recipient to send back to you?
The read receipt *request* is a header that gets added to your outbound
e-mail. The recipient's e-mail client has to recognize the header and
then send back a new e-mail as the read reciept. While the header is
well defined, what comprises a read receipt e-mail sent back to you is
not. ...
Well, I was correct on the first point that the MDN (message disposition
notification) request is enacted by adding a header, which is the
"Disposition-Notification-To" header. However, I was wrong in that
there is no standard on the content of the reply (well, there isn't
regarding the content but there regarding headers defining that
content). RFC 2298 (ftp://ftp.rfc-editor.org/in-notes/rfc2298.txt)
describes MDNs. While a header is used to ask for the reply (read
receipt), a header is used but not specifically as the read receipt
itself. Instead a MIME header is added that defines the MIME part in
the body of the email as the disposition report (read receipt). That
is, the returned email has a MIME part in it that comprises the
notification (that you can read) but that MIME part includes headers
that identify there is that MIME part in the body, so indirectly there
are headers on which you can test if an e-mail is a read receipt.
When I send an email with a read receipt, the following header gets
added to that outbound e-mail:
Disposition-Notification-To: "myName" <myEmailAddress>
When I receive that email and elect to send a read receipt, a new email
gets composed and sent that has the following in the header and body
sections:
Header section:
Content-Type: multipart/report;
report-type=disposition-notification;
Body section (in MIME part's headers):
Content-Type: message/disposition-notification
Since the MIME content is adequately defined in the headers, there is no
reason to include testing the body section for the "Content-Type:
message/disposition-notification" string. Besides, the content of that
MIME part is at the whim of the sender's e-mail program (although that
line must still appear to define that MIME part's type). Just define a
rule that looks in the message headers for BOTH the "Content-Type:
multipart/report;" and "report-type=disposition-notification;" lines.
So the rule in Outlook might look something like:
Apply this rule after the message arrives
with 'Content-Type: message/disposition-notification' in the body
and with 'report-type=disposition-notification' in the message header
<whatever action clause(s) you want to commit on that message>
<recommended 'stop processing more rules' clause>
Testing on just the "report-type" header line is probably sufficient (so
you could delete testing for the string in the body of the message).
I haven't bothered with using or sending read receipts in m-a-n-y years.
In fact, my anti-spam program will strip out the read receipt headers so
I never have to bother with them in case I forget to configure my e-mail
client to NEVER send read receipts. I had to disable that filtering to
do the testing above. I thought Outlook would get the receipt e-mail
and then update its message store (a database) to record that a read
receipt was delivered and that status change was on the record for the
original message that you sent that requested the receipt. In other
words, once the receipt got accepted by your Outlook client, it wasn't
needed anymore because the status of the original message sent out got
updated. However, as I recall, you had to actually open the read
receipt e-mail to read it which then got the record updated for the
original message to have its status updated to reflect that you got a
read receipt for it. There is some chance, probably good, that if you
move them out of the Inbox that reading them in another folder will not
get Outlook to update the status for the original e-mail. If you aren't
going to read those read receipts that YOU requested then why bother
requesting them?
I don't see why you even want to keep the read receipt e-mails after you
have read them. If the status of the original e-mail gets updated, why
keep the fluff?