Exchange 2013 public folders are sending read receipts for items viewed in public folders

Question

We have Exchange 2013 with public folders.  These public folders are used for a large amount of shared contacts.  When a user goes into the public folders and double clicks on a contact to view it, Exchange dispatches a read receipt to all users
that are configured as publishing editors to notify them that a certain contact was read.  How do I disable this option?

Answer 1

hi again dear.. :)
"At first, I would like to say the
read Receipt is not sent out by the device, it is sent out by the Exchange server. This is how it works and what happens:
1.     
E-mail with request for send
receipt is received on the Exchange server;
2.     
E-mail is synchronized with Windows Mobile based device using Exchange
ActiveSync;
3.     
When e-mail is
read on Windows Mobile based device the read status is synchronized back to the Exchange server;
4.     
The Exchange server creates and sends out the
Read Receipt when receiving the Read status update from the device;
The above is how this is implemented and there is no functionality which allows preventing this from occurring on the Mobile device.
It seems that there is an alternative method to disable RR using transport rules. However, it will at the risk of the filtering out other messages
with the same subject.
Towards the third party mobile clients that support RR and DR, you might consider using Flexmail 4.11. It’s impossible to deactivate ActiveSync
RRs in Exchange server 2007/2010."
also
One way to stop read receipts being triggered through client side configuration on the mobile is to use the option "Don't Mark Read on server".
I have tested this successfully using this option in the TouchDown mail client on Android.
Not sure if the standard or other mail clients do support this option, TouchDown certainly does and it works.
The side effect obviously is, that the read status isn't synced back to Exchange anymore:"
hope now i r clear... one way or the other... you need to send a feed back or define a transport rule... but that again may create problem with the same subject :)
Regards Shah. MCITP, MCMA, MCTS No claims (try at your own risk)