Introduction

When IMAP special folders are mapped wrong after a mailbox migration, the mail is usually still present on the server. What breaks is the folder-role mapping between the client and the destination platform.

The new server may use different special-use flags, folder names, namespaces, delimiters, or subscription defaults, so Drafts, Junk, Trash, or Archive starts pointing to the wrong path or gets recreated as duplicate folders. Treat this as a folder designation problem before assuming messages are missing.

Symptoms

  • Drafts save into the wrong folder or stop appearing where users expect them
  • Deleted messages go to an unexpected Trash or Deleted Items folder
  • Junk or Spam actions create a second folder instead of using the migrated one
  • Archive moves mail into a new folder while the old archive folder still exists
  • Webmail and desktop or mobile clients disagree on which folders are Drafts, Junk, Trash, or Archive
  • Multiple folders such as Drafts, INBOX.Drafts, Spam, Junk, Trash, and Deleted Items appear after cutover

Common Causes

  • The mailbox migration copied messages but did not preserve server-side special-use folder designation
  • The destination platform created default Drafts, Junk, Trash, or Archive folders during first login
  • The new IMAP server uses a different namespace or delimiter than the source server
  • The correct folders exist but were not subscribed after migration
  • One or more clients kept old local special-folder mappings from the previous server
  • Renamed, localized, or duplicated folders now compete for the same special role

Step-by-Step Fix

  1. Open the mailbox in webmail or the destination mail admin view and identify which folders currently hold live Drafts, Junk, Trash, and Archive content, because you need the server’s actual folder roles before correcting any client mapping.
  2. Compare the folder list for duplicates such as Drafts and INBOX.Drafts or Trash and Deleted Items, because migrations often preserve the old path and also auto-create a new default special folder.
  3. Check IMAP folder subscriptions and subscribe the correct Drafts, Junk, Trash, and Archive folders if needed, because some clients hide unsubscribed folders and then create replacements.
  4. Verify the namespace and folder delimiter used by the destination IMAP server, because a client that still targets the old path format can map special folders to the wrong mailbox name after migration.
  5. Review the server-side special-use or folder designation settings for Drafts, Junk, Trash, and Archive, because clients behave more consistently when the server advertises the correct folder roles.
  6. Reassign the special folders inside each affected mail client to the exact destination folders shown on the server, because many clients keep local Drafts, Junk, Trash, and Archive mappings from the previous host.
  7. Avoid deleting duplicate folders until the new mapping is confirmed and tested, because removing the wrong folder too early can hide where the client is still saving drafts or deleted messages.
  8. Run controlled tests for saving a draft, deleting a message, marking mail as junk, and archiving mail from webmail and one IMAP client, because each special-folder action can fail independently after a migration.
  9. Recheck every device connected to the mailbox and align them to the same folder designations, because one stale client can recreate the wrong special folders and break the mapping again.