hydroxide VS proton-bridge

There's an alternative to ProtonMail bridge at https://github.com/emersion/hydroxide

You can use it headless too. But only with a x86 CPU. For that i followed this guide. If you are using an arm CPU (e.g. Raspberry Pi) then i would suggest this application in order to send mails via your protonmail account.

If there ever were any plans I never heard about them. I did try and add I2P support to a ProtonMail bridge but it was rejected because the maintainer frankly didn't seem to understand what it was, which confused me. He seemed to think I had added some kind of WebUI(Which I hadn't) and not POP and SMTP over I2P support(Which I had). https://github.com/emersion/hydroxide/pull/199

Nope, no sync possibilities available. The alternative Proton Mail Bridge, Hydroxide started looking into CalDAV support - but that effort seems to have stranded.

Since I posted this, I was able to get the go package working by applying a patch. It is still not clear to me how I can manage my bridge passwords, though. How do I expire one of them ? Can that be done on the ProtonMail website ?

You can actually send but it is a bit complicated and you need the protonmail bridge, or https://github.com/emersion/hydroxide

I know the hydroxide project started looking into this a couple of years ago too - which should be able to do CardDAV, but it seems that the CalDAV effort stranded too.

You can check out this project: https://github.com/emersion/hydroxide

That isn't really fair. If you read the article, protonmail essentially supplied the FBI the recovery email of the account. This is metadata that protonmail must have that isn't encrypted by the user for obvious reasons.

Regarding the "MITM" for every email sent, this is related to their "bridge" software which allows regular IMAP/SMTP software to use Proton Mail. This software must edit the emails to encrypt them in their scheme.

This software is open source and can be inspected and/or built locally. https://github.com/ProtonMail/proton-bridge

> This appears to be related to a behaviour that ProtonMail has of dropping all plaintext email if any mime-encoded parts exist.

https://github.com/ProtonMail/proton-bridge/issues/26#issuec...

I'm actually more shocked knowing that they drop plain text if there is a mime-encoded part (e.g. HTML). Just verified that all mails imported from GMail and all newer mails I received in PM only have the HTML part now, while GMail shows both HTML and plain text parts in message source. Great, now if I want to use a text-only client to read those mails in the future, I won't be able to.

Now I honestly wonder, how did they think this is something okay to mess up? Is there just no usable email hosting service for someone that want their mails not touched and also stored securely? Like, this is not even going to save storage space for PM - I'm paying for my storage.

Repository here https://github.com/ProtonMail/proton-bridge

The privkey is never loaded out of the keychain. Rather, it acquires a handle to the privkey and relies on the keychain to carry out cryptographical operations. (https://github.com/ProtonMail/proton-bridge/blob/master/pkg/keychain/helper_darwin.go and https://github.com/ProtonMail/proton-bridge/blob/master/pkg/keychain/keychain_darwin.go)

Oh yes. The Bridge shouldn’t have been marketed as stable for the past years because of this issue (see issue #220 on Github, reported 2021-09-29). It’s fixed in Bridge 3.0.