When a Lotus Notes 6.5+ migration encounters items with invalid MIME Transfer Encoding, MigrationWiz attempts to fix this automatically. If the attempt to fix the MIME Transfer Encoding failures, MigrationWiz can dump the MIME header of the object(s) and save them for analysis if the Advanced Option "LotusDumpEmailHeaderOnError=1" has been enabled. This Advanced Option will dump MIME header information for items where an attempt to fix MIME Transfer Encoding fails.
An example case of MIME Transfer Encoding that will fail would be auto-generated email on Domino servers containing a corrupt (or non-standard) data format. Another instance would be a migration in which some data is missing after migration.
After enabling the Advanced Option "LotusDumpEmailHeaderOnError=1" and resubmitting the migration, the MIME header information of failed items is dumped to a file named "LotusDumpMIMEHeader.txt" on the migration server. This file is located in this location: \Users\%current_user%\AppData\Local\LotusExtractor in the most recent app- folder (example: app-1.0.00526.28586).