# Feed the password to the bridge and redirect output to /tmp # Just in case of, kill all running processes MuttRC=$HOME/fitx_confg/mutt/protonmail.muttrc OHneg=$HOME/fitx_confg/mutt/hydroxide/hydroxide It’s foolish, some people say but if you are using OpenBSD and an encrypted /home, you should be more than safe. I cannot stand writing my password every single time I check my e-mail, so that I store it locally. This is my amazing contribution to humankind. Set little “ /” that you see at the end of the second line is crucial… it took me quite a while to figure out.

Set imap_pass = 'what hydroxide auth spits as password when you start it' The third line runs SMTP server for sending email.Ī minimal configuration of muttrc must contain these lines to get it to work:.The second line runs IMAP server for receiving email.The first line authenticates and decrypts your protonmail account in memory, prompts for your protonmail password, and spits out a temporary password for the client “login” to the bridge, which is hydroxide in our case.$ GO111MODULE=on go get /emersion/hydroxide/cmd/hydroxide Note that with the current version of go in OpenBSD (go1.13.9), running Get a text-based “bridge-like” MIT-licensed programme, hydroxide: They later offered a “bridge” to use it on the most usual mailers which, as you can guess, did not include mutt. The problem so far has been that protonmail only offered a web interface or an app for smartphones and such. I have always wanted to use protonmail with mutt and OpenBSD. On the other hand, I have a protonmail account since it was created, +/- a few months. I have changed several times my affiliation, and each time I get a new e-mail account and then I need to update anything official linked to it, such as journals, committee boards, reviewer panels etc. I have been using mutt for the last ~20 years of my life.

Protonmail imap