It is definitely a pain in the ass but I’ve haven’t had any companies as far as I know block my emails yet with my setup. The biggest thing is setting up your dns correctly to prevent your emails from going straight to spam
Yah the dkim was largely what I had issues with. Mostly because it wasn’t mentioned to me that it was necessary. But once I was aware of it it was quick to fix
I was about to write that the Protonmail bridge wasn’t that great with serious long standing issues. The main one I experienced myself was the subject line being different than the body for older mails, apparently caused by message UIDs not being stable (issue 220). They did fix that in February so I’ll have to check again.
A self hosted email server for privacy while keeping thunderbird access
Otherwise protonmail is the way to go
Protonmail is paid and im dumb fpr selfhosting uwu
proton mail has a free plan
EDIT: can’t be used with thunderbird tho afaik
Precisely
Actually, it can, altough only via Protonmail Bridge
Protonmail has a free plan with a inbox size limit that 99% of people will never hit. I’ve had it since 2019 and only 15% usage of my capacity
Not a lot of other good options if you don’t self host which is a bitch even for professionals nowadays
What I mean is that you need to pay in order to remove the impossibility of using an e-mail client.
Ah you are correct. Never heard of their bridge until now
deleted by creator
It is definitely a pain in the ass but I’ve haven’t had any companies as far as I know block my emails yet with my setup. The biggest thing is setting up your dns correctly to prevent your emails from going straight to spam
deleted by creator
Yah the dkim was largely what I had issues with. Mostly because it wasn’t mentioned to me that it was necessary. But once I was aware of it it was quick to fix
I was about to write that the Protonmail bridge wasn’t that great with serious long standing issues. The main one I experienced myself was the subject line being different than the body for older mails, apparently caused by message UIDs not being stable (issue 220). They did fix that in February so I’ll have to check again.