Help menu Reference
Account import formats
Accepted list shapes, CSV columns, preview counts and import messages.
All examples are made up. Paste a list or open a file in Accounts → Add accounts → Import a list to see a preview before anything is saved. Keep real lists private.
Plain lists#
Write one account per line. The character right after the email address separates the fields: a colon, comma, pipe, semicolon or a real tab. Spaces alone don't. Blank lines and lines that start with # are skipped. A repeated address keeps its first line, and addresses are lowercased.
buyer@example.com:FAKE_PASSWORD
buyer@example.com,FAKE_PASSWORD
buyer@example.com|FAKE_PASSWORD
buyer@example.com;FAKE_PASSWORD
For tab-separated data, use a real tab. When separators inside a password make a line ambiguous, use CSV.
Proxy and incoming-server endings#
buyer@example.com:FAKE_PASSWORD:proxy.example.com:8080
buyer@example.com:FAKE_PASSWORD:proxy.example.com:8080:fake_user:fake_pass
buyer@example.com:FAKE_PASSWORD:fake_user:fake_pass:proxy.example.com:8080
buyer@example.com:FAKE_PASSWORD:fake_user:fake_pass@proxy.example.com:8080
buyer@example.com:FAKE_PASSWORD:socks5://fake_user:fake_pass@proxy.example.com:1080
buyer@example.com,FAKE_PASSWORD,proxy.example.com:8080:fake_user:fake_pass
buyer@example.com:FAKE_PASSWORD:imap.example.com:993
| End of the line | Mailman reads it as |
|---|---|
host:port with port 993 or 143 | Your provider's incoming-mail server, not a proxy |
host:port with any other port | A proxy |
host:port:user:pass | A proxy with a login. It wins when user:pass:host:port would also fit |
user:pass:host:port | A proxy with a login, when exactly one password field comes before it |
user:pass@host:port | A proxy with a login |
http://, https:// or socks5:// URL | A proxy of that type. The login is optional, or can be a username only |
For a proxy on port 993 or 143, write the full URL. For a bare ending, set Proxies without a scheme are to your supplier's type. Encode reserved characters in a URL login, and put IPv6 addresses in brackets, as in socks5://[2001:db8::1]:1080. Only HTTP, HTTPS and SOCKS5 routes work.
A password can contain colons, but a recognized ending can change how its line is read. Use CSV for ambiguous values.
Saved sign-in permissions#
Some Outlook lists hold a refresh token, which is saved permission to sign in, and a client ID. Treat the token like a password.
buyer@outlook.com:REFRESH_TOKEN:00000000-0000-4000-8000-000000000000
buyer@outlook.com:FAKE_PASSWORD:REFRESH_TOKEN:00000000-0000-4000-8000-000000000000
| Rule | Detail |
|---|---|
| Recognized when | The token is longer than 100 characters and the client ID has hex digits in groups of 8-4-4-4-12 |
| Second form | The extra password is dropped. Use CSV to keep it for browser sign-in, or to add a proxy or client secret |
| Company domains | Mailman asks Microsoft whether the domain is a work or school directory. If so, a token line imports as Microsoft 365. A password line stays a plain IMAP account |
CSV template#
- Select CSV template. The supported headers and made-up rows appear.
- Select Copy or Save template, or select Use template to fill the paste box.
- Replace the example rows. Save as CSV and select it with Browse….
Category,Provider,Username,Password,App Password,Host,Port,Mail Proxy,Browser Proxy,OAuth2 Refresh Token,OAuth2 Client ID,OAuth2 Client Secret,Recovery Email,Email Aliases,2FA Secret Key
Examples,Custom,buyer@example.com,FAKE_PASSWORD,,imap.example.com,993,,,,,,,,
The first row must begin Category,Provider,Username,Password; that is how Mailman tells an AYCD file from a plain list. It finds the other columns by name, so blank cells are fine. Quote cells that contain commas or newlines.
| Column | What Mailman does |
|---|---|
| Category | The account's group. Older exports and the template keep this header |
| Provider | Ignored. Mailman detects the provider from the address |
| Username | The email address. Required |
| Password, App Password | The sign-in. Needed unless both OAuth2 columns are filled in. App Password wins |
| OAuth2 Refresh Token, OAuth2 Client ID | Needed together. The pair wins over any password |
| OAuth2 Client Secret | Optional, kept with the pair |
| Host, Port | A custom incoming server. Port is a number from 1 to 65535 |
| Mail Proxy, Browser Proxy | One proxy route. Mail Proxy wins |
| Recovery Email | The account's recovery address |
| Email Aliases | Separated by spaces, newlines, semicolons, commas or pipes. Invalid and repeated aliases are dropped, so check the saved account |
| 2FA Secret Key | A base32 secret, not a current six-digit code |
Extra columns don't import passkeys, sending settings or message history.
Read the preview#
| Preview shows | It means |
|---|---|
| "New" | Lines that will be added |
| "duplicates" | Repeats of an address earlier in the list. Each is marked "Duplicate in list" |
| "problems" | Lines Mailman can't import, each with a reason |
| "Already added" | Addresses already in Mailman |
| "OAuth", "password", "app password" | How many accounts sign in each way |
| "aliases" | Aliases found, and how many accounts have them |
| "Outlook sync" | How many Outlook accounts will be "Realtime" and "On demand" |
| "with no known IMAP host" | Addresses on a domain Mailman doesn't know. Add a server to those lines |
Select Copy invalid to copy the bad lines, or Copy problems to copy the reasons. Both can contain private details. Turn on Update passwords of accounts already added to replace the passwords and tokens of matching accounts. Nothing is duplicated, and the preview shows how many credentials will change.
Messages#
| Message | Cause | Fix |
|---|---|---|
| "invalid email address" | The line doesn't start with a complete address | Use an address such as buyer@example.com |
| "missing credential" | Nothing usable follows the address | Add the password, or both token fields |
| "invalid proxy" | The proxy part has no valid shape | Use a full shape such as http://proxy.example.com:8080 |
| "invalid port" | A port isn't a number from 1 to 65535 | Enter the port your provider or supplier gave you, such as 993 for an incoming server |
| "unrecognized import line" | The character after the address isn't a separator, or a field is empty | Cut the line to buyer@example.com:FAKE_PASSWORD, then add fields one at a time |
| "invalid base32 2FA secret" | The 2FA secret isn't base32 | Correct or remove it |
Wait for a fresh preview after each correction. XLSX, JSON and saved email files are not account imports; see Add a list of email accounts for file and import messages.