A question that comes up often enough to merit a post is: "How does one block read receipts from leaving or entering my org?" Good question. I'm glad you asked! And to answer that we need t...
Published Feb 23, 2011
Version 1.0
Blog Post
5 MIN READ
Everything you wanted to know about read receipts and delivery reports but were (understandably) afraid to ask
@tomkern: The problem is that there is no prompt since the server sends the message and not a client. I know it's the same store and I don't want to filter RR requests just stop Exchange from automatically sending them.
I've played around with a raw connection to the server opened with openssl s_client and as soon as I send the following IMAP command to the Exchange server (a05 is the current command number and 31 is the message number in the current folder):
a05 fetch 31 body[text]
the exchange server sends the RR reply. The only expected result is to get the message body and add the "seen" flag to the message. There is no client involved in this test that can send the RR-message.
The exchange server also adds the recipient account name to the response telling the spammer the name associated with the email address. God to have for them to personalize the next spam message.
I've played around with a raw connection to the server opened with openssl s_client and as soon as I send the following IMAP command to the Exchange server (a05 is the current command number and 31 is the message number in the current folder):
a05 fetch 31 body[text]
the exchange server sends the RR reply. The only expected result is to get the message body and add the "seen" flag to the message. There is no client involved in this test that can send the RR-message.
The exchange server also adds the recipient account name to the response telling the spammer the name associated with the email address. God to have for them to personalize the next spam message.