John G wrote:

Pray tell ! How.

And if the message has been recived what tracking is there that I could not
do by looking in the folder where I would like a rule to put them all.

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. The recipient can send anything back they want as the read
receipt. Normally the user gets stuck with whatever their e-mail
program hardcoded to send back as the new e-mail for the read receipt
but that doesn't eliminate users that can use scripting to manufacture
their own read receipt e-mails and obviously different e-mail programs
may compose a different new e-mail as their read receipt that they send
back to you. So you end up creating a rule in which you will have to OR
several strings as you continue receiving back the read receipts to
handle whatever they choose to send back to you. There isn't a standard
header that they can add to their new e-mail that identifies that it is
an acknowlegement to your request (for a read receipt).

Since many anti-spam programs can strip out the read receipt header from
inbound e-mails, and since most users soon disable read receipts after
getting the first few, using read receipts is mostly a waste of time
unless you are in a closed environment where you can force all
recipients to keep read receipts enabled, like in a company where its
policy dictates that read receipts will be honored for company e-mail;
however, it is likely that they strip out the read receipt header for
inbound e-mails that come from the outside since they don't want their
employees sending them outside the company.