IMAP Migration

Question

Hi, we are attempting to migrate our emails from our IMAP mail server using the Exchange 365 Migration tool.

The parameters set for your migration endpoints are correct, I was able to synch a single account.

When I attempt to further migrate the other accounts, I get the following message:

Error: MigrationTransientException: We were unable to reach your email provider. Please check your server settings, or try again later. --> We were unable to reach your email provider. Please check your server settings, or try again later. --> Connection has shut down. --> A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call

I have checked with our mail provider, and they maintain that the parameters used are correct and that nothing is blocked on their side.

Providing that they are correct, does anyone have any idea what could prevent the syncing?

Thank you kindly,

Jeremy

Answer 1

Hi Jeremy,

This issue was posted to the Service Health Dashboard (SHD) as incident EX196753 Start time: Monday, November 25, 2019, at 6:41 PM UTC. User Impact: Admins may see a Transient error message when attempting to migrate users from a specific third-party service.

Current status: We're monitoring the incremental sync, but have requested additional information from your representatives to continue troubleshooting based on the continued slowness of the sync.

Tenant administrators can view current information and updates on SHD at the link here

https://portal.office.com/AdminPortal/Home#/servicehealth

If you are experiencing a similar issue and do not see an SHD post, please let us know by sharing your tenant information via Private Message (PM) as this may indicate either a scoping issue or an independent problem.

For affected customers to easily identify the information here, this thread will be closed. You may subscribe to this thread or refer to SHD for updated information. I will also post back here once the issue is resolved on SHD.

Best regards,

Shyamal

Answer 2

Hi Jeremy,

Service Health Dashboard has indicated that issue EX196753has been resolved as of: Monday, December 9, 2019, at 4:00 AM UTC. If you are still experiencing an issue, please let us know  or post a new thread in our category as this may indicate either a scoping issue or an independent problem.

Best Regards,

Sylvie