Moving a mailbox between clients on macOS, Windows, and Linux usually starts with hostnames and ports. The breakage shows up later, when folders appear twice, messages look unread on one machine and read on another, or a Sent folder quietly stops syncing. Folder delimiters are the usual culprit. This listicle walks through the configuration points worth comparing across platforms, and it adds one item most setup guides skip: discovering the delimiter your server actually uses before any client writes a folder name.
Compare the protocol before you compare the client
Every cross-platform comparison should start at the protocol layer, because the client is only as predictable as the protocol underneath it. IMAP keeps mail on the server and synchronizes folders and read states across devices, which is why it survives a move from Outlook on Windows to Apple Mail on macOS to Thunderbird on Linux without losing state. POP3 downloads mail to a single client, supports inbox only, and leaves folder structure to whatever that one machine invents. SMTP handles sending mail in both cases, so it rarely causes the folder problems people blame on it.
The port choices are settled by now. IMAP uses encrypted port 993, POP3 uses encrypted port 995, and STARTTLS on 143 or 110 is the fallback when the encrypted ports are blocked. What matters for a platform comparison is that these numbers are identical everywhere, so a port mismatch is easy to spot. Delimiter mismatches are not, because no port or checkbox exposes them.
One workflow deserves a separate note. SEO automation tools default to POP3 because they want a simple inbox feed and do not care about folders. That is fine until the same account is also opened in a desktop client over IMAP, at which point the POP3 client’s “leave messages on server” setting decides whether the two views stay consistent. If you are evaluating POP3 for SEO automation, confirm the fetch tool does not delete after download unless you intend it to.
The delimiter discovery step
IMAP servers announce their folder hierarchy separator in the LIST response, usually as a single character: a dot on some servers, a slash on others. IMAP4rev2, defined by RFC 9051, keeps this behavior from the older spec, and RFC 1939 for POP3 has nothing to say about folders at all because POP3 has no concept of them. Clients that hardcode the delimiter create duplicate folders when moved across platforms, so the comparison checklist needs a line item for reading the separator before you create anything.
You can see the separator without special tools. In a terminal, a quick `openssl s_client -connect host:993` session followed by a tagged `LIST “” “*”` command returns the hierarchy line. Thunderbird exposes it in the server settings under Advanced. Outlook hides it, which is part of why Windows-to-Linux moves go wrong: the user never sees what the server reported.
A configuration checklist across the major platforms
Treat each platform as a set of defaults you are overriding, not a fixed environment. The goal is one account definition that behaves the same in Outlook, Apple Mail, Thunderbird, and a mobile client, and that means writing down the incoming mail server, the outgoing mail server, the authentication method, and the delimiter before touching any client.
Authentication comes first in practice. Most providers now require OAuth2 or app passwords, and a client that only offers plain password auth will fail on one platform while working on another. Confirm the method per client before debugging folders, because a login failure and a folder failure look similar to a frustrated user but have nothing in common.
Folder behavior comes second. Decide whether Sent, Drafts, Trash, and Junk map to server folders or to local ones. IMAP clients that map them locally will not synchronize those folders across devices, so a message sent from the phone never appears in the desktop Sent folder. Set the special-folder mapping explicitly on each platform rather than accepting the default.
The table below compares the common configurations you will meet when moving a mailbox between platforms. It is not exhaustive, but it covers the trade-offs that decide whether a move goes cleanly.
| Configuration | Protocol and ports | Folder behavior | Best for |
|---|---|---|---|
| Full IMAP sync | IMAP on 993, SMTP on 465 or 587 | Server folders and read states sync; delimiter read from LIST | Multi-device users, shared project mailboxes |
| POP3 fetch to one machine | POP3 on 995, SMTP on 465 or 587 | Inbox only; folders are local to that client | SEO automation tools, archive-and-delete workflows |
| IMAP with local Sent and Trash | IMAP on 993, SMTP on 465 or 587 | Inbox syncs; Sent and Trash stay on one device | Single primary machine with occasional mobile check |
| POP3 with leave messages on server | POP3 on 995, SMTP on 465 or 587 | Inbox duplicated across clients; no read-state sync | Transition periods before a full IMAP cutover |
| Catch-all domain on IMAP | IMAP on 993, SMTP on 465 or 587 | All addresses land in one hierarchy; delimiter must match | Project inboxes, AllMail catch-all domains |
Where delimiter mismatches actually bite
The failure pattern is consistent. A user sets up an account in a client that assumes a slash, the server reports a dot, and the client creates “Sent” while the server already has “Sent” under a different path. The result is two Sent folders, one of which receives nothing. On the next platform the client reads the server hierarchy correctly and shows both, and the user assumes mail is being lost.
The same issue appears with nested project folders. A catch-all setup, such as AllMail providing catch-all domains for projects, often builds a hierarchy like Clients.Acme.Invoices or Clients/Acme/Invoices depending on the server. A client that hardcodes the wrong separator creates a parallel tree rather than writing into the existing one. Rules and filters then fire against one tree and not the other, and the symptom looks like a broken filter when it is really a naming problem.
Cross-platform moves make this worse because clients differ in how they handle a mismatch. Thunderbird tends to respect what the server reports. Some Outlook configurations and a number of mobile clients assume the delimiter from the account type rather than the LIST response. Apple Mail generally follows the server but has its own quirks with special folders. None of these behaviors is wrong in isolation; the problem is that they disagree.
There is a practical test. Before migrating, create a test folder on the server with the correct separator, subscribe to it in each client, and confirm all clients see one folder rather than two. If duplicates appear, the client is not honoring the delimiter and you should fix the account definition before importing mail. Doing this on a test folder costs five minutes; doing it after a migration costs an afternoon of merging duplicate trees.
POP3 accounts sidestep the issue entirely because there are no server folders to name. That is one reason POP3 for SEO automation is so common: the fetch tool only needs the inbox, and the delimiter question never arises. The trade-off is that the same account cannot be used meaningfully on a second device, and any folder organization you do is local and invisible to the automation.
For a final pass, write the delimiter into your account documentation alongside the hostnames and ports. Note the protocol, the encrypted port, the authentication method, and the separator character. When the next platform arrives, the checklist starts from known values instead of guesswork, and the duplicate-folder problem stays where it belongs: in the past. The AllMail blog covers related setup details if you want the server-side view of the same problem.
{“@context”:”https://schema.org”,”@type”:”Article”,”headline”:”Cross-Platform Mail Setup: Watch the Folder Delimiter”,”description”:”Cross-platform mail setup fails when clients hardcode folder delimiters. Discover how ‘.’ vs ‘/’ causes duplicate folders and how to avoid it.”,”inLanguage”:”en”,”datePublished”:”2026-11-16T20:00:22Z”,”articleBody”:”Moving a mailbox between clients on macOS, Windows, and Linux usually starts with hostnames and ports. The breakage shows up later, when folders appear twice, messages look unread on one machine and read on another, or a Sent folder quietly stops syncing. Folder delimiters are the usual culprit. This listicle walks through the configuration points worth comparing across platforms, and it adds one item most setup guides skip: discovering the delimiter your server actually uses before any client w”}
