fkrebs
a2f1d49170
- CT 111 (dev): Gitea + Coder + act-runner migrated to CT 104 - Gitea uses Redis for queue/cache/session (idmapped NFS LevelDB workaround) - Zoraxy routes dev/git updated to 192.168.1.40 - AdGuard dev.nuclide.lan updated to 192.168.1.40 - CT 112 (secrets): Infisical migrated to CT 109 - DB dump restored; SITE_URL updated to 192.168.1.8:8200 - AdGuard secrets.nuclide.lan updated to 192.168.1.8 - Proton Mail Bridge deployed on CT 104 (SMTP :1025, IMAP :1143) - Homepage updated: Dev group → ct104, Infisical → my-local, Background group added - portmap, ct-inventory, zoraxy, dev-environment, secrets-manager all updated Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
Proton Mail Bridge
Headless Proton Mail Bridge running on CT 104 — exposes ProtonMail account as SMTP/IMAP endpoints for local services (n8n, Infisical, etc.).
Stack
- Host: CT 104 (
docker, 192.168.1.40),/opt/stacks/proton-bridge/docker-compose.yml - Image:
shenxn/protonmail-bridge:latest - SMTP:
192.168.1.40:1025 - IMAP:
192.168.1.40:1143 - Config volume:
proton-bridge_proton_config
Initial login (one-time, interactive)
ssh root@192.168.1.40
docker exec -it proton-bridge /bin/bash
protonmail-bridge --cli
# Commands: login → (enter Proton credentials) → list (note bridge SMTP password)
# exit
After login the bridge stores credentials in the volume and runs headlessly on restart.
SMTP credentials for other services
Once logged in, run list inside the CLI to get:
- SMTP host:
192.168.1.40 - SMTP port:
1025 - SMTP user: your Proton email address
- SMTP password: the bridge-generated password (not your Proton login password)
- IMAP host:
192.168.1.40 - IMAP port:
1143
Ops
# CT 104
cd /opt/stacks/proton-bridge
docker compose up -d --force-recreate proton-bridge
docker logs proton-bridge -f