hydroxide VS protonmail-bridge-docker

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

The ticket above is referenced from this ticket in the github repo you point at: https://github.com/shenxn/protonmail-bridge-docker/issues/75

I know this one is an issue, and for that you will want to use an email client with the bridge. I have used a protonmail docker container shenxn/protonmail-bridge-docker with imapfilter to provide client side filtering.

This should do the trick if you don't mind Docker

If this is more for personal use within your home lan network, try installing https://github.com/shenxn/protonmail-bridge-docker on your NAS and then configure all your local computers (and nas) to use the lan ip/port of the running docker container, acting as your mail server.

If you can use docker, the easiest way is to use something like https://github.com/shenxn/protonmail-bridge-docker.

version: "3.6" services: bridge: build: https://github.com/shenxn/protonmail-bridge-docker.git#:build container_name: pm-bridge restart: unless-stopped volumes: - "/data/docker/protonmail:/root" ports: - "1025:25" - "1143:143"