Package Details: protonmail-bridge 1.8.12-1

Git Clone URL: (read-only, click to copy)
Package Base: protonmail-bridge
Description: Integrate ProtonMail paid account with any program that supports IMAP and SMTP
Upstream URL:
Keywords: bridge email mail protonmail protonmail-bridge
Licenses: GPL3
Conflicts: protonmail-bridge-bin
Submitter: aimileus
Maintainer: ali.molaei (PMBridge-Devs)
Last Packager: ali.molaei
Votes: 84
Popularity: 1.16
First Submitted: 2018-03-02 16:03
Last Updated: 2021-12-15 09:02

Pinned Comments

bthompson commented on 2021-06-17 04:13

Just having pass installed with a key set up wasn't enough for me, I had to follow this:

ali.molaei commented on 2020-04-16 07:52

This package is now being built from source. if you want the binary version, use protonmail-bridge-bin package

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

ali.molaei commented on 2021-03-04 20:22

@Spixmaster I'm well aware of this issue, if you read the comments, I mentioned it before :)

Actually, this commit is fixed the issue, But it's not included in the latest tag

Spixmaster commented on 2021-03-04 19:58

The package is not building.

go: downloading v0.0.0-20200117012304-6edc0a871e69
go: downloading v0.0.0-20200323222414-85ca7c5b95cd
/home/user/.go/pkg/mod/ no required module provides package; to add it:
        go get
/home/user/.go/pkg/mod/ no required module provides package; to add it:
        go get
make: *** [Makefile:172: prepare-vendor] Fehler 1
==> FEHLER: Ein Fehler geschah in prepare().
    Breche ab...
error making: protonmail-bridge

ali.molaei commented on 2021-03-01 09:12

@captainfeeny thanks for letting me know a new tag is on GitHub, but I'm not gonna update this package until this issue gets fixed

I can fix it temporarily in the PKGBUILD but I don't, the reason is it makes the PKGBUILD specific to some versions and makes it not a general script.

And also, On the website, the latest version is still 1.6.3, so I will wait until at least it changes

ali.molaei commented on 2021-02-23 06:20

I've got a Flag Out-of-date message from @lpc123 with this comment:

Issue is with go install -v -tags=no_env

First, this is a comment, not an Out-of-date report, please don't do this. Second, thanks to check for the problem, but Makefile is not built by me, please report the problem upstream

By the way, I made an issue there now:

tinwasp commented on 2021-02-19 16:49

Same issue here: lost my account settings with my last update from 1.5.7-1 to 1.6.3-1. This may have happened before but certainly not with the last half dozen updates or so. Decided to downgrade again to 1.5.7-1; now everything's back. Not sure, what the new version does differently.

RonObvious commented on 2021-02-19 13:03

I've found a work-around -- but be warned, it might be dangerous.

I checked the "issues" in the github site for the bridge, and saw several things that were a little similar, but not exactly the problem we've been discussing. However, I did find a reference to the directory "~/.password-store", and found two subdirectories in ~/ .password-store/protonmail-credentials" on my machine. One of the subdirectories was rather old.

So, I tried removing the "~/.password-store" directory (or rather, I moved it to a different name, so I could restore it if needed). After restarting the bridge, and reconfiguring Thunderbird (since I now had new passwords to give to TBird), I can close the bridge and my account is still there when I restart the bridge. I also tried logging out and back in (my "normal" way to close and reopen the bridge), and my account is still there.

So, apparently, in my case at least:
1) protonmail-bridge is the only application using the "~/.password-store" directory and
2) it can get poisoned, but
3) removing it and logging in all over again (to protonmail, and then to Tbird) fixes everything.

This workaround will (obviously (?)) not work if some other application is using the "~/.password-store" directory. Presumably, just eliminating the "protonmail-credentials" subdirectory would be safer, but I can't say whether that would also fix the problem.

RonObvious commented on 2021-02-19 11:46

@cybr8 -- Regarding "pass init": I used my protonmail address as the 2nd argument, i.e. "pass init".

However... I'm still having problems. I can get the bridge up and running, for exactly one session, but if I "close the bridge" and restart it, my account is gone. I've tried clearing the cache and clearing the keychain (using the bridge, after "adding an account"), but I can't the bridge to restart the way it used to.

I'm not at all sure that this has to do with PKGBUILD or AUR or arch, I will go check to see if proton has some kind of website like this one -- but if any other arch/AUR users are also having this problem, and find a solution, I'd love to hear about it. Sorry for bothering everyone who is NOT having this problem.

By the way, I'm using fairly vanilla gnome, and am usng the bride with Thunderbird, for what that's worth.

cybr8 commented on 2021-02-18 09:15

I ran into the same issue as @RonObvious and tried the "pass init" command but didn't succeed. I now get: "credential store: exit status 1: gpg: Fehler beim automatischen holen von '<my-protonmail-address>' Meldungen: Allgemeiner Fehler, Allgemeiner Fehler" still trying to fix this.

hakayova commented on 2021-02-18 03:12

is there anyone else with the same issue?

This happens to me every once in a while with protonmail-bridge-nogui but not with protonmail-bridge. Even more commonly, i.e. with every reboot, I need to stop the bridge service, run protonmail -c confirm that I am logged in via info (occasionally I am not), quit out and restart bridge service. If I need to login again, sometimes the server password is regenerated and I have to change email client settings accordingly. It is annoying but simple to work with and provides an important service, I can live with it. I am sorry for hijacking the thread.

eimis commented on 2021-02-17 10:03

is there anyone else with the same issue?

just updated to 1.6.3 and it's fine, didn't ask me to log in again or anything