• Edited by CCaldwell Wednesday, June 26, 2013 9:02 PM I can't spell

Hi

Maybe you can logon public folder mailbox and cancle it.

File>>Options>>Mail>>Tracking>>uncheck "Read receipt confirming the recipient a read receipt request"

hello CC.

Read receipt is sent when the "Do not send delivery reports" option is selected in Exchange Server

http://support.microsoft.com/kb/324636?wa=wsignin1.0

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. Its 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 :)

As far as I can think of, a contact item should not have a read receipt attached to it. What I can think of is that the content of public folders has been converted incorrectly and somehow being understood as a mail item by Exchange.

You said, the migration was not successful; what do  you mean by that? Did you move the PF content (contacts) to the new PF mailboxes using PST import?

Use MFCMAPI and logon to PF mailbox. See the what the message class on the contact items. It should appear as IPM.Contact but anything else. PR_READ_RECEIPT_REQUESTED property on a IPM.Note (Normail Email) determines whether a red receipt is requested or not. This property should not exist on a IPM.Contact class. Let me know if you require any assistance on finding out the options.

Milind,

   Thanks for the response I used the tool you mentioned and looked at the public folders as suggested.

They do show up as the IPM.contact type. I found one of the contacts that had generated a read receipt and found that there is a PR_READ_RECEIPT_REQUESTED property on it and it was set to true. All of the contacts contained this property but only some were set to true.

I took a screen shot but my account hasn't been verified yet so I couldn't post it.

Thanks,

    Tim



Tim, that sounds interesting. I never saw that prop having set to True on a contact object. How many contact items are there in this mailbox? If not many; you can perform a backup of all contacts into a PST file or any other preferred way and remove this prop on these items and then see whether the read receipts are still generated.

I will try to figure a way to perform a bulk operation if you have too many contact items in that folder but can't promise right away.

In my case, most of the Exchange migration was successful with the exception of public folders. I was not surprised though because the old Exchange server (2007) was a mess. So after burning up two days trying to get the PFs to migrate to the new server, I simply exported the public folder data to a PST via an Outlook client. After creating the new PFs in 2013 I just imported everything from the PST and reconfigured permissions. Not ideal but it only took a couple hours vs. not getting anywhere with the migration.

With everything being imported to new PFs all items appeared as new/unread items.  So when they were being viewed the Exchange server was sending read receipts.

I apologize but at this point I can't recall exactly how I resolved this.  I'll have to go back through my notes to see what I did.

You pretty much described the exact thing that happened to us; we were coming from 2003 SBS though. Public Folders failed and we ended up exporting from an outlook client and then importing as you described.

I really wished I could recall how I resolved this issue. It was one of those issues that irritated me so much, by the time I got it resolved I flushed the entire problem from my memory.

For some reason I think it had something to do with delegates or user permissions on the public folders.  I'm still reviewing the server to see if I can find what it was that fixed it.  If I find something i'll follow up for sure.

Tim, that sounds interesting. I never saw that prop having set to True on a contact object. How many contact items are there in this mailbox? If not many; you can perform a backup of all contacts into a PST file or any other preferred way and remove this prop on these items and then see whether the read receipts are still generated.

I will try to figure a way to perform a bulk operation if you have too many contact items in that folder but can't promise right

I am also experiencing a similar issue.  However, in my situation the read receipts indicate the items have been deleted without being read.  The source of these messages is a public folder mailbox that only contains public folder hierarchy data.

My public folder data was successfully migrated from Exchange Server 2007 SP3 RU10 to Exchange Server 2013 CU3 (CU4 was applied afterwards).

Unfortunately, my company has over 3500 public folders, so it's difficult to determine the folder these items were deleted from.

I'd appreciate any direction anyone can provide.

Hello, 

we have the same issue after migration from Exchange 2007 SP3 UR14 to Exchange 2013 CU9. 

Any new information about this issue and how to resolve this?

the Script from "Milind Naphade " is an good idea. is it really just for the "Public Folder Contacts"?

Can't find the "Public Folder" connection part in die Script. Or do i have to use for email adresse the public folder mailbox email adress?

Thanks, 

Best, 

Martin