RFC-822 Compatible Format Error

The requested message could not be converted to an RFC-822 compatible format: This error is caused by a well-known bug in the IMAP implementation used by your email server. This typically affects Exchange IMAP servers. The bug is documented here: http://support.microsoft.com/kb/938650.

Internally, each IMAP message is assigned a unique ID (UID). MigrationWiz retrieves UIDs from the Destination server as a way to prevent creation of duplicates when performing multi-pass migations. Because of the bug in some IMAP implementations, MigrationWiz is unable to retrieve UIDs from the IMAP server.


Upgrade Your IMAP Server

Consider upgrading your IMAP server to a version which contains a fix for this well-known bug (see Knowledge Base article referenced above).

Disable Duplicate Detection

If your IMAP server cannot be upgraded, and the IMAP server reporting the error is the Destination server (not the Source server) for your migration, the following workaround can be used:

  1. Sign in to your MigrationWiz account.
  2. Click on Mailbox Migration.
  3. Click on Migrate Mailbox.
  4. Select your Mailbox Project.
  5. Click on View Mailboxes.
  6. Select your Mailbox.
  7. Click on Edit Mailbox.
  8. Click on Show Advanced Options.
  9. Checkmark the box for Do not search Destination for duplicates.
  10. Click on Save​.

By disabling the search for duplicates, MigrationWiz stops fetching UIDs from the Destination server. As a result, the error is not encountered. Note that duplicate prevention is still in effect, but only as long as you use the same mailbox object. For example, if you perform multiple migrations using the same MigrationWiz mailbox record, no duplicate will be created. However, we cannot guarantee protection against duplicates if you recreate the MigrationWiz mailbox record.

Use Another Email Protocol

If the IMAP Exchange server is Exchange 2003, 2007 or 2010, consider selecting Exchange as the Source or Destination protocol instead of IMAP on your project. This will allow content to be migrated using a non-IMAP protocol. Keep in mind however than changing the protocol may result in creation of duplicates if prior content was already migrated. Therefore we recommend that you first clean up your Destination mailbox.

Was this article helpful?
0 out of 0 found this helpful