Proton Bridge CLI

Rikudou_Sennin's picture
Submitted by Rikudou_Sennin on Sat, 2025/12/20 - 15:37
Rating: 
5
Your rating: None Average: 5 (1 vote)

Proton Bridge (CLI only) packaged for SailfishOS. Also includes a systemd service which you can enable using:

systemctl --user daemon-reload (only the first time)
systemctl --user start proton-bridge.service

Note that the way it works is pretty idiotic and you have to stop it before you can configure it:

systemctl --user stop proton-bridge.service

Then you can get configuring:

proton-bridge --cli

Configuring

When inside the interactive shell, use help command for instructions. But the basic flow:

  • login - to store an account
  • info - to print the connection details

When you run the info command, you will get a similar output:

Configuration for you@example.com
IMAP Settings
Address:   127.0.0.1
IMAP port: 1143
Username:  you@example.com 
Password:  <random-string> 
Security:  STARTTLS

SMTP Settings
Address:   127.0.0.1
SMTP port: 1025
Username:  you@example.com 
Password:   <random-string>
Security:  STARTTLS
 

These are the settings you can use in any IMAP/SMTP email client, like the Jolla built-in Email app. Some apps (like Thunderbird for Android) manage to pre-fill everything except the password automatically, with others (like the Jolla Email app) need to be configured manually.

Category:

Keywords:

Application versions: 
AttachmentSizeDate
File proton-bridge-3.21.2-1.aarch64.rpm10.93 MB11/12/2025 - 16:29
File proton-bridge-3.21.2-2.aarch64.rpm10.93 MB20/12/2025 - 15:36
Changelog: 

- The app now requires libsecret to install

Comments

sturai's picture

sturai

Sun, 2025/12/21 - 23:24

Proton Bridge CLI on Sailfish OS (OP6/enchilada): keychain packages missing + workaround / notes

 

Hi,

First of all, thank you for packaging Proton Bridge CLI for Sailfish OS — it’s great to see this available on OpenRepos.

Device / setup

  • Device: OnePlus 6 (enchilada) – Sailfish OS community port
  • Proton Bridge CLI package: proton-bridge-cli (OpenRepos)
  • Use case: local IMAP/SMTP on 127.0.0.1 for Sailfish Mail

What happens
When running:

proton-bridge --cli

I initially got warnings/errors about the keychain / secret service:

  • “Failed to open secretservice session: The name org.freedesktop.secrets was not provided by any .service files”
  • “Could not load/create vault key … no keychain”
  • “Proton Mail Bridge is not able to detect a supported password manager (secret-service or pass). Please install and set up a supported password manager and restart the application.”

On my port (enchilada), package managers don’t provide the usual dependencies:

  • gnome-keyring (Secret Service provider) is not available
  • pass / password-store is not available either
    So Bridge can’t find a supported password manager out of the box.

Workaround / current status
Despite the above, I managed to get Bridge configured and working (IMAP/SMTP reachable locally) after doing the configuration steps and restarting the service, but the lack of a proper Secret Service / pass backend is still confusing and I’m not sure what the “best practice” is on Sailfish ports without those packages.

Questions / suggestions

  1. Is there a recommended Sailfish-friendly way to satisfy Bridge’s keychain requirement on devices where org.freedesktop.secrets (gnome-keyring) and pass are not available?
  2. Would it make sense to document this limitation in the package description (ports with minimal repos), and maybe suggest an alternative (e.g. running bridge on another machine + SSH tunnel) if no keychain backend is installable?
  3. If you have a known-good package set (e.g. libsecret + a secret service provider) that works on Sailfish, I can test it on OP6/enchilada and report back.

I’m happy to provide logs (proton-bridge --cli output, systemctl --user status proton-bridge.service, etc.) if you tell me what you need.

Thanks again!