<div>
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.<br />
<br />
I have recommended this question be closed as follows:<br />
<br />
Accept: 'Imtiaz Hasham' (<a href="https:#a42898193" rel="ugc">https:#a42898193</a>)<br />
<br />
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.<br />
<br />
seth2740<br />
Experts-Exchange Cleanup Volunteer
</div>


<div>
<div class="content wysiwyg-content">
Hello,<br />
<br />
We are migrating an Exchange 2010 cu17 (CAS/HUB separated to MBX roles) environment to &nbsp;exchange 2016. We are still in the coexistence phase with some mailboxes being migrated to 2016 cu6.<br />
<br />
The problem is that, a transport rule exist for some users, when they send emails outside the org to request approval from a moderator. The moderator receives twice the email for approval, and he needs to accept it twice for the same email sent.<br />
After a few tests, we noticed that when the sender is still hosted on 2010 that the problem occurs, not for 2016 mailboxes, wherever the moderator mbx is hosted.<br />
<br />
I tried to recreate the rule on 2016, &nbsp;migrated to moderator mailbox to 2016, test it on a lab with older CU for 2016 and 2010 (CAS/HUB/MBX role), same same.<br />
<br />
Any idea what is happening please? There is a lot of mailboxes to migrate, it will take time.<br />
<br />
Thank you.<br />
<br />
Regards,
</div>
</div>


Hello,

We are migrating an Exchange 2010 cu17 (CAS/HUB separated to MBX roles) environment to  exchange 2016. We are still in the coexistence phase with some mailboxes being migrated to 2016 cu6.

The problem is that, a transport rule exist for some users, when they send emails outside the org to request approval from a moderator. The moderator receives twice the email for approval, and he needs to accept it twice for the same email sent.
After a few tests, we noticed that when the sender is still hosted on 2010 that the problem occurs, not for 2016 mailboxes, wherever the moderator mbx is hosted.

I tried to recreate the rule on 2016,  migrated to moderator mailbox to 2016, test it on a lab with older CU for 2016 and 2010 (CAS/HUB/MBX role), same same.

Any idea what is happening please? There is a lot of mailboxes to migrate, it will take time.

Thank you.

Regards,

Exchange 2010 2016 coexistence emails issue

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.