2024-07-07 18:02:45 +00:00
|
|
|
# ProtonMailBridge plus PostFix
|
|
|
|
|
2024-07-07 19:31:25 +00:00
|
|
|
## Security:
|
|
|
|
* GPG stores in-container are set up in a wildly insecure way.
|
|
|
|
* Compose creates a volume for /root with these stores to preserve bridge cache.
|
|
|
|
* Therefore, entire setup is extremely insecure.
|
|
|
|
* All because GPG unlock handling in bridge is still broken upstream as of 2024.
|
2024-07-07 18:02:45 +00:00
|
|
|
|
|
|
|
## Setup
|
|
|
|
|
2024-07-07 19:31:25 +00:00
|
|
|
Note docker-compose.yaml contains a debian image. This is only for testing inter-container mailing/networking.
|
2024-07-07 18:19:08 +00:00
|
|
|
|
2024-07-07 19:31:25 +00:00
|
|
|
Build only seems to require `#usermod -aG docker username`. Not tested as root/sudo.
|
2024-07-07 18:02:45 +00:00
|
|
|
|
2024-07-07 19:31:25 +00:00
|
|
|
By default, `bridge` runs in non-interactive mode on container startup. You must set up the bridge initially:
|
|
|
|
|
|
|
|
cp .env.example .env
|
2024-07-07 20:16:12 +00:00
|
|
|
vi .env
|
2024-07-07 19:31:25 +00:00
|
|
|
docker-compose build
|
|
|
|
docker-compose up -d
|
2024-07-07 18:02:45 +00:00
|
|
|
docker-compose exec pmb bash
|
|
|
|
killall bridge
|
|
|
|
./bridge -c
|
|
|
|
|
2024-07-07 19:31:25 +00:00
|
|
|
When in bridge cli mode:
|
2024-07-07 18:19:08 +00:00
|
|
|
|
|
|
|
* `login` will activate account.
|
|
|
|
* `info` will show creds to input into host filesystem .env postfix values.
|
|
|
|
|
2024-07-07 22:36:14 +00:00
|
|
|
Then:
|
2024-07-07 22:36:56 +00:00
|
|
|
|
2024-07-07 19:31:25 +00:00
|
|
|
exit
|
|
|
|
docker-compose down
|
|
|
|
vi .env
|
|
|
|
docker-compose up -d
|
|
|
|
|
|
|
|
Note: docker-compose down && docker-compose up are necessary. "restart" will not reload .env
|
2024-07-07 18:02:45 +00:00
|
|
|
|
|
|
|
## msmtp test
|
|
|
|
|
2024-07-07 18:21:15 +00:00
|
|
|
vi ~/.msmtprc
|
2024-07-07 18:02:45 +00:00
|
|
|
echo "test" | msmtp -a pmb recipient@recipient.email
|