Operating system:: Windows 10 (64bit)
Outlook version: 2019, classic 2024
Email type or host: IMAP
Outlook version: 2019, classic 2024
Email type or host: IMAP
INCIDENT: During migration of an IMAP email account to Outlook 2024, a large-scale message duplication occurred on the server, nearly filling the mailbox quota (9.1/9.9 GB).
INFRASTRUCTURE: I have several devices that have access to one mailbox via IMAP:
If anyone has any idea what I did wrong or what a better way to fix this would be, let me know.
INFRASTRUCTURE: I have several devices that have access to one mailbox via IMAP:
- My old PC (Outlook 2019)
- My new PC ("classic" Outlook 2024), which I wanted to connect
- My Android Phone (which uses Android's standard Mail app)
- I can also access this mail account directly in the browser (very limited web UI).
- Initial State (March 12, 2025):
- Inbox: 22,712 messages
- PST backup available from right before the migration (There seems to be some issues with the file, but after opening it in PST Walker and exporting it again, I can see all the messages inside of it in Outlook without issue.)
- Normal email operation, all devices (minus the new PC) work together without issue
- Migration Process (March 13, 2025):
- Installed Outlook 2024 on a new PC
- Set up IMAP account
- Imported PST file from Outlook 2019
- Switched to Online Mode, started sync
- Observed "synchronization problems" folder growing rapidly
- Error codes mentioned frequently in the messages of this folder are [8004DF0B-0-0-322] (for individual messages) and [8004DF0B-0-0-560] (for folders)
- Sync took forever, cancelled
- Deleted account, set up fresh account without PST import, sync took forever again, cancelled again
- Post-Incident State
- Suddenly discovered: Inbox (server side) now has 33,800 messages (+11,088 duplicates)
- Duplicates have minor differences (missing new lines, "'" around receiver names, one message marked with "replied to", the other one not)
- 4 messages show even bigger signs of corruption (mangled headers, wrong dates)
- After syncing Outlook 2019 the duplication occurred there as well. Had to abort because it was taking forever.
- Contacting server provider: No server side back ups available, I'm on my own.
- Accessing the mailbox via Thunderbird over IMAP (in order to have more control than just via WebUI). This took forever to sync but is working to this point. No duplication issues there.
- Installing a deduplication extension in Thunderbird. Not possible because all of them are only compatible with older versions of Thunderbird.
→ Currently trying this again because I found the last compatible version of Thunderbird as a Portable Apps release.
- Used an Outlook deduplication tool (MAPILab Duplicate Email Remover) to remove duplicates from the Outlook 2019 mailbox (slightly suboptimal solution as some messages were not just duplicated, but also corrupted), tried syncing to the server again, which caused even more duplicates to appear (now 9.2/9.9 GB taken). I'm scared.
- On a (much) smaller mailbox I tried the following clean slate approach semi-successfully:
- Deleted all older messages from the server including duplicates (possible via Web UI or Thunderbird)
- Deleted all older messages from my local Outlook 2019 installation
- Synced both systems → no more sync errors
- Now I copied all older messages from the PST (which doesn't have duplicates) to the correct Outlook 2019 folder.
- Synced Outlook 2019 to the server and Thunderbird. No sync issues still.
- This worked for the Notebooks but my Android phone (even after deleting and readding the IMAP account) still doesn't understand what exactly happened and doesn't show me most of my messages from 2024 and 2025; when I refresh, the latest messages disappear.
- Another small disadvantage of this approach: Copying messages from the PST to Outlook somehow changes their encoding (?) causing emojis in subject lines to be shown as "??" in Thunderbird and the WebUI.
- I'm having scruples using this approach on my main account as it would mean I have to delete tons of messages.
If anyone has any idea what I did wrong or what a better way to fix this would be, let me know.