ProtonMail
/
proton-bridge
mirror of https://github.com/ProtonMail/proton-bridge
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
258 Commits 6 Branches 130 Tags 19 MiB
Go 50.8%
C++ 18.7%
Gherkin 17.7%
QML 9.1%
Shell 1.1%
Other 2.6%
Go to file
Michal Horejsek 4973e38748 Import-Export app everywhere 2020-08-24 10:11:51 +02:00
.github/ISSUE_TEMPLATE Update issue templates 2020-04-29 07:57:01 +02:00
cmd Import-Export app everywhere 2020-08-24 10:11:51 +02:00
doc Import-Export app everywhere 2020-08-24 10:11:51 +02:00
icon.iconset We build too many walls and not enough bridges 2020-04-08 12:59:16 +02:00
internal Import-Export app everywhere 2020-08-24 10:11:51 +02:00
pkg Import/Export final touches 2020-08-24 10:11:51 +02:00
release-notes Release notes for Import-Export 2020-08-24 10:11:51 +02:00
test Import/Export final touches 2020-08-24 10:11:51 +02:00
utils Keep Import-Export credits up to date 2020-08-24 10:11:51 +02:00
.gitattributes We build too many walls and not enough bridges 2020-04-08 12:59:16 +02:00
.gitignore Shared GUI for Bridge and Import/Export 2020-08-24 10:11:50 +02:00
.gitlab-ci.yml Import/Export final touches 2020-08-24 10:11:51 +02:00
.gitmodules We build too many walls and not enough bridges 2020-04-08 12:59:16 +02:00
.golangci.yml Import/Export backend prep 2020-08-24 10:11:50 +02:00
BUILDS.md Shared GUI for Bridge and Import/Export 2020-08-24 10:11:50 +02:00
CONTRIBUTING.md We build too many walls and not enough bridges 2020-04-08 12:59:16 +02:00
COPYING.md fix 404 errors by using absolute urls 2020-04-30 09:12:26 +00:00
Changelog.md Import/Export final touches 2020-08-24 10:11:51 +02:00
LICENSE We build too many walls and not enough bridges 2020-04-08 12:59:16 +02:00
Makefile Fixing IE icon 2020-08-24 10:11:51 +02:00
README.md Import-Export app everywhere 2020-08-24 10:11:51 +02:00
go.mod Import/Export GUI 2020-08-24 10:11:51 +02:00
go.sum Import/Export GUI 2020-08-24 10:11:51 +02:00

README.md

ProtonMail Bridge and Import Export app

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.

Description Bridge

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.

Description Import-Export app

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.

Keychain

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.

Environment Variables

Bridge application

  • BRIDGESTRICTMODE: tells bridge to turn on bbolt's "strict mode" which checks the database after every Commit. Set to 1 to enable.

Dev build or run

  • APP_VERSION: set the bridge app version used during testing or building
  • PROTONMAIL_ENV: when set to dev it is not using Sentry to report crashes
  • VERBOSITY: set log level used during test time and by the makefile

Integration testing

  • 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 accounts
  • TAGS: set build tags for tests
  • FEATURES: set feature dir, file or scenario to test

Files

Database

The database stores metadata necessary for presenting messages and mailboxes to an email client:

  • Linux: ~/.cache/protonmail/bridge/<cacheVersion>/mailbox-<userID>.db (unless XDG_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

Preferences

User preferences are stored in json at the following location:

  • Linux: ~/.cache/protonmail/bridge/<cacheVersion>/prefs.json (unless XDG_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

IMAP Cache

The currently subscribed mailboxes are held in a json file:

  • Linux: ~/.cache/protonmail/bridge/<cacheVersion>/user_info.json (unless XDG_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

Lock file

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 (unless XDG_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

TLS Certificate and Key

When bridge first starts, it generates a unique TLS certificate and key file at the following locations:

  • Linux: ~/.config/protonmail/bridge/{cert,key}.pem (unless XDG_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