Airpost
Help

Data and files

Where Airpost keeps your profile, what's in it, where passwords are stored, and how to back up, move or start over.

Everything Airpost keeps on your computer lives in one profile folder, plus one item in your system keyring. The desktop app, the engine, the airpost command and the MCP server all use the same profile, so they all see the same mail and settings. For how the pieces share it, see Profiles and data.

Your profile folder

PlatformLocation
macOS~/Library/Application Support/Airpost
Linux~/.config/Airpost (or $XDG_CONFIG_HOME/Airpost)
Linux snapThe snap’s $SNAP_USER_COMMON folder

Airpost uses its own profile, separate from Mailspring’s, so the two can run side by side. Developer > Open Engine Logs opens the profile folder in your file manager.

The CLI and other tools accept a different profile with --config-dir <DIR> or the AIRPOST_CONFIG_DIR environment variable. That’s how you run a second, separate setup, for example a test profile:

airpost --config-dir ~/airpost-test status

What’s inside

PathContents
config.jsonYour desktop preferences.
settings.jsonSettings the engine keeps for every client: undo send, the default sending account, signatures and so on. Read and change them with airpost settings get and airpost settings set.
accounts.jsonThe engine’s list of accounts and their connection settings. No passwords.
keymap.jsonShortcuts you changed, on top of the shortcut set. See Keyboard shortcuts.
airpost.dbThe local mail database and search index. Usually the largest file.
templates/Your templates, one file each.
packages/Plugins and themes you installed.
mcp.jsonMCP settings from Preferences > MCP. See Agents.
mcp-audit.logA record of what MCP agents did. See Agents.
run/The running engine’s socket (engine.sock) and discovery file (engine.json), which clients use to find it.
engine-<accountId>.logThe engine’s log for each account.
engine.logThe background engine’s log for work not tied to one account.
secrets.encOnly on machines without a keyring: encrypted credentials.

Logs

Each log rotates at 5 MB, keeping up to three older copies (.log.1 to .log.3). Each line has this shape, in local time, with levels info, warning, error and critical:

<pid> [YYYY-mm-dd HH:MM:SS.mmm] [<thread>] [<level>] <message>

The engine records only its own messages at info level and above, not those of the libraries it uses, so logs stay readable and don’t contain message bodies. To read them from a terminal:

airpost logs                  # the account's log (with --account, or the only one)
airpost logs me@example.com -n 100
airpost logs engine -f        # follow the background engine's log
airpost logs gateway          # the web gateway, if you run one

Passwords and keys

Account passwords, sign-in tokens, and AI and integration keys are held by the engine in one item in the macOS Keychain or the Linux Secret Service (GNOME Keyring, KWallet and others). They aren’t written to the profile in plain text, and the desktop window never holds them: it asks the engine to act.

On a machine without a keyring, such as a server, the engine can keep them encrypted in secrets.enc instead, sealed with a key file you point it at (AIRPOST_ENGINE_KEY_FILE). See Background services.

Backing up and moving

Your mail stays on your provider’s server, so on a new computer you only need to add your accounts again; Airpost downloads the mail. To keep your settings, templates, rules and plugins:

Stop everything

Quit Airpost. If you turned on Keep Airpost running in the background, or installed the engine as a service, stop it too (airpost engine stop).

Copy the profile folder

Copy the whole folder. You can leave out the logs and, if you don’t mind downloading mail again, airpost.db.

Sign in again on the new computer

Credentials are in the old computer’s keyring, not the folder, so each account will ask you to Reconnect.

To keep a copy of actual mail outside your provider, export it:

# One message as .eml
airpost export <message-id> -o message.eml

# A whole folder as mbox (mboxrd)
airpost export --mbox --folder INBOX -a me@example.com -o inbox.mbox

Exports are made from the server’s copy, so they’re complete even if Airpost only downloaded part of a message. The desktop has the same as Export folder as mbox.

Starting over

WhatWhereEffect
Rebuild one accountPreferences > Accounts > the account > Rebuild…, or airpost account resync <account>Deletes that account’s local mail and downloads it again.
Rebuild everythingPreferences > Advanced > Rebuild the mail databaseDownloads mail again for every account. Accounts and settings stay.
ResetPreferences > Advanced > Reset Airpost… (Remove all accounts and settings)Removes all accounts and settings. Mail on your providers isn’t touched.
Remove an accountPreferences > Accounts > the account > Remove…, or airpost account remove <account>Removes it from this computer, with its stored credentials.

airpost account remove keeps the account’s downloaded mail unless you pass --delete-data, so adding the same account back later is quick. None of these change anything on your mail provider.

Bringing over a Mailspring profile

Preferences > Accounts > Import from Mailspring imports from a Mailspring profile on the same computer. The button only appears when Airpost finds one.