Gpg -dearmor -output debsig.gpg bridge_pubkey.gpg Import the public key into keyring by following these instructions: There is no point going to all the trouble of doing this in a secure method with ProtonMail if we are just doing to download a Deb file and trust it.ĭownload the public key `bridge_pubkey.gpg` Sudo apt-get install debsig-verify debian-keyring gdebi-core pass Ubuntu 21.04, 20.04, 21.10 How did I do this? Install Bridge In order to do this, I need to be able to point them to something, if the webserver is not there and ProtonMail doesn’t support relay then I needed some way of sending notifications to these new Protonmail emails. I run a lot of homelab type services which send out emails as notifications.

However, the issue I have is a simple one. I migrated to ProtonMail mainly on Peer pressure however I was using it a while back, and I wanted to make things a little more secure. If you’re looking for a well thought out free (for 5 domains) Mailserver I would strongly recommend Axigen. Up until last night I was hosting my own Axigen mail server for 3 domains running in a cloud-hosted VM. I also can’t spend hours working out certificates for other ports.

I’m using port 25 as the mail relay is internal only, it’s not public-facing and it’s not needed to be encrypted. I’m then going to use postfix as a mail relay on port 25 (not encrypted) to move mails through the ProtonMail bridge to my proton mail accounts. What I’m going to go through is to set up the ProtonMail Linux bridge in CLI mode as a service that will sit and listen on port 1025 for SMTP.

You may read this title and think “That’s oddly specific” which to a degree it is. Bash, blog, homelab, howto, linux, selfhosted

Protonmail smtp server address