mopajewish.blogg.se

Next, I found that the service’s free tier includes what I needed to get started with this low-volume blog. The Proton website stepped me through the several changes I needed to make to my DNS records ( registered through DreamHost, as always), to first verify I owned the domain, and then to enable the SPF, DKIM, and DMARC authentication features for Email. Since I already had a “Mail Plus” level account there, this didn’t cost me anything more. To start, I configured my custom domain name () in my account so I could create email addresses within it.

I found a solution that is still secure and not privacy-invasive. That is to install the ProtonMail “Bridge” application on the server hosting WordPress, and send through that.

There is a somewhat well-known and unsupported workaround which others have blogged about using.Yet philosophically, I refused to use Gmail, MS Live email, or any other popular “free” email service that’s part of the global Surveillance Economy just to work around this technical limitation.Therefore, it appears at first that you can’t use Proton accounts at all with WordPress.The automatic encryption system they use depends on their own client software. The ProtonMail service intentionally does not support SMTP. I wanted my domain’s email to be hosted by Proton.I wanted those emails to come from an address for consistent branding.I needed my WordPress site to be able to send outgoing emails, both to me as the system administrator, and potentially to subscribers, contributors, etc.

But when I launched this Thinking Privacy blog site, using WordPress, I encountered an apparent dilemma caused by these coincident facts: I have been using and recommending the privacy-centric ProtonMail (now branded ) to friends, family, and colleagues for many years.