https://github.com/sdelafond/docker-protonmail-bridge
Run ProtonMail Bridge in a docker container
https://github.com/sdelafond/docker-protonmail-bridge
docker docker-compose imap imap-server protonmail protonmail-bridge smtp smtp-server
Last synced: 12 months ago
JSON representation
Run ProtonMail Bridge in a docker container
- Host: GitHub
- URL: https://github.com/sdelafond/docker-protonmail-bridge
- Owner: sdelafond
- License: mit
- Created: 2019-06-20T12:06:52.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2023-07-17T12:46:36.000Z (almost 3 years ago)
- Last Synced: 2025-04-24T20:42:33.702Z (about 1 year ago)
- Topics: docker, docker-compose, imap, imap-server, protonmail, protonmail-bridge, smtp, smtp-server
- Language: Shell
- Size: 13.7 KB
- Stars: 39
- Watchers: 4
- Forks: 8
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
Run ProtonMail Bridge in a docker container
Usage
=====
Starting the service
--------------------
1. get the Debian package for the bridge from ProtonMail, and save it in
the current directory
2. create your env file from the default one
```
cp default-env .env
```
3. edit .env to add your ProtonMail credentials; you can leave out
PROTONMAIL_EXTRA_2FA blank: since that value depends on time, you'll
instead want to specify it when running the service
4. start the service
```
PROTONMAIL_EXTRA_2FA= docker-compose up
```
Configuring your email client
-----------------------------
For credentials, use the "Username: " and "Password: "
that the service prints when it start.
The URL for the IMAP service is `localhost:2143`, and the SMTP one is
`localhost:2025`.
Client compatibility
--------------------
The ProtonMail Bridge officially supports Thunderbird only, but using
offlineimap or fetchmail works just fine. Here's an example
.fetchmailrc:
```
set daemon 15
defaults
fetchall
# keep
poll 127.0.0.1 service 2143 with protocol imap auth password
user there is seb here
password
```
SSL certificates
================
SMTP
----
Full certificate information:
```
echo | openssl s_client -connect localhost:2025 -starttls smtp | openssl x509 -noout -text
```
Fingerprints:
```
echo | openssl s_client -connect localhost:2025 -starttls smtp | openssl x509 -noout -fingerprint -md5
echo | openssl s_client -connect localhost:2025 -starttls smtp | openssl x509 -noout -fingerprint -sha1
echo | openssl s_client -connect localhost:2025 -starttls smtp | openssl x509 -noout -fingerprint -sha256
[...]
```
IMAP
----
Full certificate information:
```
echo | openssl s_client -connect localhost:2143 -starttls imap | openssl x509 -noout -text
```
Fingerprints:
```
echo | openssl s_client -connect localhost:2143 -starttls imap | openssl x509 -noout -fingerprint -md5
echo | openssl s_client -connect localhost:2143 -starttls imap | openssl x509 -noout -fingerprint -sha1
echo | openssl s_client -connect localhost:2143 -starttls imap | openssl x509 -noout -fingerprint -sha256
[...]
```
Credits
=======
Thanks to Hendrik Meyer for socat+setcap workaround described at
https://gitlab.com/T4cC0re/protonmail-bridge-docker