How to unify sent folders between Roundcube and Outlook without losing IMAP history

When every IMAP client uses a different sent folder, history becomes a puzzle: Sent, Sent Items, Enviados, Itens Enviados. In a corporate environment, this impacts auditing, support, and operational search. This guide shows the correct way to consolidate without losing messages.

Technical root cause#

Roundcube and Outlook may create/mark sent folders with distinct names, especially when:

1. Client language changes (PT/EN);
2. Account was configured on multiple devices at different times;
3. There was a server migration without Special-Use flags standardization.

Step 1: Define a canonical folder on the server#

I choose a single official folder, for example Enviados (or Sent), and make it the reference for all clients.

In Roundcube:

1. Settings;
2. Special Folders / System Folders;
3. Sent messages pointing to Enviados.

Step 2: Consolidate legacy history#

Before touching Outlook, move legacy content to the canonical folder.

Example of a safe workflow:

1. Create a local backup (PST/OST or IMAP export);
2. Move messages from Sent and Sent Items to Enviados;
3. Wait for complete synchronization;
4. Validate final item count.

Step 3: Map Outlook to the existing folder#

In Outlook:

1. Account Settings;
2. More Settings;
3. Sent Items tab;
4. Select Save sent items in the following folder on the server;
5. Choose Enviados.

Then, restart Outlook and force synchronization.

Operational validation#

Checklist I use at the end:

• [ ] Sending via Roundcube lands in Enviados
• [ ] Sending via Outlook lands in Enviados
• [ ] Sending via mobile lands in Enviados
• [ ] No new duplicate folders appeared
• [ ] Searching by sender returns unified history

Common issues after unification#

Outlook keeps creating "sent items"#

Cause: old profile in cache or local client policy. Action: review profile, re-validate the sent folder, and clear account cache.

Messages "disappear" after moving#

Common cause: incomplete synchronization or offline cache limit in Outlook. Action: wait for total sync, review IMAP status and, if necessary, reduce move batches.

Preventive best practices#

1. Single language standard for special folders;
2. Mapping documentation per tenant;
3. Post-email migration validation before releasing to end users.

IMAP validation via command line (advanced optional)#

When I need to prove it at the protocol level, I validate folder listings and special flags with a text-mode IMAP client (e.g., via openssl).

Simplified flow:

openssl s_client -connect mail.example.com:993 -crlf

Then I authenticate and list mailboxes to confirm which folder is marked for sent on the server. This avoids diagnosis based solely on client UI.

Incident closure checklist#

1. Canonical folder defined in webmail;
2. Outlook mapped to existing folder;
3. History consolidated and checked;
4. End-user validated web/desktop/mobile sending;
5. Ticket closed with synchronization evidence.

Production takeaways#

Unifying Sent/Enviados is a simple adjustment but with high operational impact. When standardized on the server and replicated on clients, it eliminates history fragmentation and reduces recurring support incidents.

See also

Email Auditing Dovecot and Exim logs: investigating disappeared email folders

Email Fixing critical Roundcube webmail slowness

Servers Anatomy of a cascading failure: from spam IP blocks to Roundcube debugging in cPanel

This post is licensed under CC BY-NC.