Encryption in transit is pretty much solved these days with TLS, what OP wants is E2E - encryption from sender to recipient with no intermediate parties having an idea about contents of the message. Problem with E2E is inconvenience: emails are inaccessible without private keys and key management is pain. Users don’t want additional headache of managing their keys between bajillion of devices where they might use emails
get a domain name, host stalwart somewhere and set up email with this new domain there, get receipt emails there and autoforward it to your main email with S/MIME, gpg or whatever enabled.
usual disclaimer ‘do not host your email blablabla’ (at least don’t get fucking digitalocean ‘droplet’ for it), but there’s no other way around that, ecommerce won’t enable shit.
I stand corrected, thank you!
Appreciate the effort, but without categories it’s not going to sail too far.
Right now it’s just a long list of everything that it’s out there, awesome-selfhosted is much more usable for looking up what you need.
Also, did you join any kind of affiliate programs/partnerships for these “10% off” green boxes? If so, would be great to disclose it. Nothing bad with getting some cash, but community will just appreciate the honesty.
Programming knowledge is largely irrelevant, as in to gain sensible benefits from it you have to be generalist software engineer with decade+ of experience of seeing it all. Then yeah, you can read any code, any stack traces and figure out the intent of developers of the system and what is undocumented/incorrectly documented.
Focusing on one particular language is the right and wrong answer at the same time. Wrong in a sense that you’ll have to pick up other languages along your journey anyway and right because you need to achieve mastery in one of them to get to more advanced programming topics. Pick a language that you have fun using and don’t care about anything else.
As for what to learn for self-hosting… Linux (pick a distro, let’s say ubuntu LTS w/o gui, ssh there and get comfortable with it. It includes installation, filesystems, RAID setups), networking, HTTP/S (that’s the main thing you’ll be interacting with as self-hoster and knowing various nuances of reverse proxying is a must), firewalling, basics of security and hardening, docker, monitoring, backups.
why not? it’s not like there is any competition.
Microsoft is making more money off Linux with Azure than several red hats combined.
with mass services requiring mandatory phone number binding I think being in user mass is a viable option - you cannot get reliable “secondary” email anymore and people don’t look through data leak dumps by eyes anyway, script doesn’t care about email address string - it all becomes hash anyway. Whois protection is pretty reliable to divert snooping 3rd-parties.
As for expensive… yeah, sad state of affairs is that there’s nothing cheap about hosting your own infrastructure. Price of not really trusting anyone or having obscure technical requirements.