Can't send mail to public folder after migrating from Exchange Server 2007 to 2013

Consider the following scenario：

• Microsoft Exchange Server 2007 is installed in a child domain. 
• You migrate public folders from Exchange Server 2007 to Exchange Server 2013 by using cutover migration. A portion of these public folders are mail-enabled.
• You send mail to the mail-enabled public folders that you migrated.

In this scenario, mails are stuck in the queue, and you receive with following error message:

You also find that the Mail setting for these mail-enabled public folders is “Disabled” in the Exchange control panel.

To work around this issue, follow these steps:

1. Enable the Mail settings for the public folders. This process creates new objects for the public folders in the Microsoft Exchange System Objects (MESO) container in the root domain.
   
   
2. Remove the old public folder objects from the MESO container in the child domain. For example, the following screenshot shows the MESO container for the child domain Corp.FabriKam.com that Exchange Server 2007 installed.
   
   
3. Because two MESO objects were created, the email address of the migrated public folder will get changed. After the old MESO object is removed, check the new object that was created in the MESO container in the root domain, and then change the email address to the original email address.

Unlike Exchange Server 2007 and Exchange Server 2010, Exchange Server 2013 always creates the public folder object in the root domain's MESO container, whether Exchange Server 2013 is installed in the root domain or a child domain. 

After migrating public folders to Exchange Server 2013, the server can't create a MESO object in the root domain, as the object is already present in the child domain's MESO container. Therefore, the migrated public folder shows a disabled state.