Email Migration

Fix ImapNoResponseException in MDaemon to Office 365 Migration

Nimra MalikNimra Malik Nov 22, 2026 868 views

Question details

Resolve repeated IMAP errors that stop an MDaemon to Office 365 mailbox migration.

Fix ImapNoResponseException During MDaemon to Office 365 Migration
Product
Microsoft 365 Exchange Online and MDaemon
Device & OS
not provided
Scenario
An administrator is migrating mailboxes from MDaemon to Office 365 using an IMAP migration batch.
Observed behavior
Messages continue copying for a time, but repeated ImapNoResponseException errors eventually lead to TooManyTransientFailureRetriesPermanentException.
Before you start

Identify the affected migration batch and accounts in the Exchange admin center. Make sure you have access to the MDaemon administration settings and the migration reports.

Solution 1Recommended

Check and correct MDaemon public-folder access

Use this approach when migration reports show inaccessible public folders or source accounts have lookup-only access to them.

In the reported case, public folders with lookup-only access contributed to the errors even though messages were still copying. Removing access to those folders allowed synchronization to complete.

1
Review the migration report

In the Exchange admin center, open Migration, select the affected batch, and review the failed user's migration report for public folders marked as having no access.

2
Inspect source permissions

In the MDaemon administration console, check the affected account's access to public folders, especially folders with lookup-only or limited permissions.

3
Adjust folder access

In MDaemon's public-folder permission settings, exclude access to the problematic public folders or correct their permissions as appropriate. Avoid granting broader access than the account needs.

4
Restart and verify

Return to Migration in the Exchange admin center and restart the affected batch, or create a new batch if necessary. Check the batch status and confirm that the source emails have synchronized to the target mailboxes.

Check and correct MDaemon public-folder access
Public-folder access: Removing access can affect what the source account can see. Coordinate permission changes with the MDaemon administrator and review any public-folder migration needs separately.
Free Microsoft Office alternative

Review migration documentation with WPS Office

WPS Office is a free, lightweight alternative for working with office documents during and after a migration. Its familiar interface and Microsoft Office format support make it easy to move existing files into your workflow. It does not fix Exchange Online migration errors or migrate mailboxes.

Review migration notes and reports saved as documents or spreadsheetsOpen and edit Microsoft Office formats such as DOCX and XLSXUse a familiar interface to ease the transition from Microsoft OfficeWork with a free, lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Why does the migration copy messages before it fails?

Some messages can synchronize while the migration encounters repeated errors on other folders. Check the affected user's report in the Exchange admin center for inaccessible public folders and the final failure details.

Can lookup-only public-folder access cause this error?

It did in the reported MDaemon migration. Check public-folder permissions in the MDaemon administration console, then remove access to problematic folders or correct their permissions before restarting the migration.

How do I get a detailed migration report?

Connect to Exchange Online PowerShell and run Get-MigrationUserStatistics -Identity user@domain.com -IncludeReport | Format-List, replacing the address with the affected user.

Does WPS Office fix the IMAP migration error?

No. The error must be investigated in Exchange Online and the MDaemon source environment. WPS Office can help you review migration documentation saved in compatible document or spreadsheet formats.