Simplify Proton Mail Bridge configuration
I have a growing list of self-hosted services, and am moving toward unattended installation and reinstallation. Proton Mail Bridge creates a challenge as it wants to be configured using an interactive CLI. Using the 'expect' utility doesn't work well because of the way log messages are presented. Providing the inputs via stdin is fragile for items such as imap-security (not idempotent) and autoupdate (confirmation prompt only when changing). I'd like to see a better way to set this up.
- Either use a plain-text file for general Bridge configuration, or commands that are idempotent and don't require confirmation (e.g. 'set imap-security ssl')
- Instead of logging in to the Bridge and generating imap/smtp passwords there, allow creating/generating this password in Proton account settings. (This would solve the TOTP problem, and also allow the password to be stable in case the Bridge needs to be reinstalled.)
1
vote