The result is listed in the below screen shot.
It's very clear that after content DB attached to new farm, the entries from source configuration DB tableEmailEnabledLists are not recreated after content DB attached. As a result, we have two woraround to fix this issue.
configuration DB tableEmailEnabledLists. You could verify by querying the table. The following code snippet you could use to reset the email alias.
You should add try and catch to your code and follow development best practice. Hope this could help you to migrate content with email enabled list to different farm.