Copyright (c) 2020 Proton Technologies AG
This repository holds the ProtonMail Bridge application. For a detailed build information see BUILDS. For licensing information see COPYING. For contribution policy see CONTRIBUTING.
ProtonMail Bridge for e-mail clients.
When launched, Bridge will initialize local IMAP/SMTP servers and render its GUI.
To configure an e-mail client, firstly log in using your ProtonMail credentials. Open your e-mail client and add a new account using the settings which are located in the Bridge GUI. The client will only be able to sync with your ProtonMail account when the Bridge is running, thus the option to start Bridge on startup is enabled by default.
When the main window is closed, Bridge will continue to run in the background.
More details on the public website.
ProtonMail Import-Export app for importing and exporting messages.
To transfer messages, firstly log in using your ProtonMail credentials. For import, expand your account, and pick the address to which to import messages from IMAP server or local EML or MBOX files. For export, pick the whole account or only a specific address. Then, in both cases, configure transfer rules (match source and target mailboxes, set time range limits and so on) and hit start. Once the transfer is complete, check the results.
You need to have a keychain in order to run the ProtonMail Bridge. On Mac or Windows, Bridge uses native credential managers. On Linux, use Gnome keyring or pass.
BRIDGESTRICTMODE
: tells bridge to turn onbbolt
's "strict mode" which checks the database after everyCommit
. Set to1
to enable.
APP_VERSION
: set the bridge app version used during testing or buildingPROTONMAIL_ENV
: when set todev
it is not using Sentry to report crashesVERBOSITY
: set log level used during test time and by the makefile
TEST_ENV
: set which env to use (fake or live)TEST_APP
: set which app to test (bridge or ie)TEST_ACCOUNTS
: set JSON file with configured accountsTAGS
: set build tags for testsFEATURES
: set feature dir, file or scenario to test
The database stores metadata necessary for presenting messages and mailboxes to an email client:
- Linux:
~/.cache/protonmail/bridge/<cacheVersion>/mailbox-<userID>.db
(unlessXDG_CACHE_HOME
is set, in which case that is used as your~
) - macOS:
~/Library/Caches/protonmail/bridge/<cacheVersion>/mailbox-<userID>.db
- Windows:
%LOCALAPPDATA%\protonmail\bridge\<cacheVersion>\mailbox-<userID>.db
User preferences are stored in json at the following location:
- Linux:
~/.cache/protonmail/bridge/<cacheVersion>/prefs.json
(unlessXDG_CACHE_HOME
is set, in which case that is used as your~
) - macOS:
~/Library/Caches/protonmail/bridge/<cacheVersion>/prefs.json
- Windows:
%LOCALAPPDATA%\protonmail\bridge\<cacheVersion>\prefs.json
The currently subscribed mailboxes are held in a json file:
- Linux:
~/.cache/protonmail/bridge/<cacheVersion>/user_info.json
(unlessXDG_CACHE_HOME
is set, in which case that is used as your~
) - macOS:
~/Library/Caches/protonmail/bridge/<cacheVersion>/user_info.json
- Windows:
%LOCALAPPDATA%\protonmail\bridge\<cacheVersion>\user_info.json
Bridge utilises an on-disk lock to ensure only one instance is run at once. The lock file is here:
- Linux:
~/.cache/protonmail/bridge/<cacheVersion>/bridge.lock
(unlessXDG_CACHE_HOME
is set, in which case that is used as your~
) - macOS:
~/Library/Caches/protonmail/bridge/<cacheVersion>/bridge.lock
- Windows:
%LOCALAPPDATA%\protonmail\bridge\<cacheVersion>\bridge.lock
When bridge first starts, it generates a unique TLS certificate and key file at the following locations:
- Linux:
~/.config/protonmail/bridge/{cert,key}.pem
(unlessXDG_CONFIG_HOME
is set, in which case that is used as your~/.config
) - macOS:
~/Library/ApplicationSupport/protonmail/bridge/{cert,key}.pem
- Windows:
%APPDATA%\protonmail\bridge\{cert,key}.pem