Hello @ all,

we have a strange problem since we migrated from Exchange 2010 public folders to 2013 public folders.

We have a single public folder mailbox containing all public folders. This mailbox resides in a database which is replicated to a second Exchange Server.

We use a mail-enabled public folder for receiving technical requests from our customers. We have configured a rule in the folder assistant which sends an auto-reply to the sender and forwards every mail to a specific distribution group. Mails in the folder are changed (i.e. color category, marked as finished, a.s.o.).

Every time, a mail is changed, a duplicate is created in the folder (with the change made before) and therefore forwarded to the distribution group. This is very annoying as we change mails very often (assign to another colleague, enter comments, a.s.o.).

If we disable the rules in the Folder assistant, everything works fine. No duplicates are generated.

We use Exchange 2013 CU3.

Any idea?


Best regards

Ben

@Ben - did you ever manage to get anywhere with this one? We are having the same problem by us and so for a mail people are receiving copies for each change. What I have noticed is that the Message-ID changes when you make a change to the email. To explain:

1. Mail is received and is "allocated" to someone in the department. This is done by adding that persons name to the subject of the mail

2. A support ticket is logged in our in house software and the mail subject has the ticket added to it and the mail is then moved into a backup folder

We have an in-house app the hooks into the subject and searches for the ticket number and if resolved saves the mail away and a bunch of other stuff. This used to be handled my making use of the Message-ID which, even after making the changes as noted above, used to always stay the same. Since moving onto Exchange 2013 the Message-ID changes for each change made - it's as if the new mail item is saved and the old one deleted. This can be proved by changing the subject of a mail sitting in the public folder, saving the mail item (but not closing it) then making another change to the subject where you are then prompted something along the lines of the item not existing (any longer).

Hello Chris,

nope, no change. Seems as if the Exchange developer team does not know yet of this "bug" as even CU7 does not fix it. I hoped that someone would get in touch with them (support case) but unfortunately...

Good news is that you know what is the cause of this error. :-) I think that only Microsoft will be able to solve this as we cannot change such Exchange behaviour... Maybe there is some idea behind this?

Has anyone heard from MS on a fix for this?

We are experiencing the same issue.

Thanks