they get even more revenue from other peoples contributions.

thats the whole point not more, not less.

so there is no point for “you” to pay them anything.

did you as a “premium customer” thought to be “the customer”? really? remember how little you personally pay for the service. it is mainly the ad companies who are youtubes “customers”. when you pay them for something, you only increase yt’s revenue, not more, not less, but you are not “the customer”, you are the product ;-)

for some reasons idk i’ld like to see a “first gentlemen” to enter the scene

i’ld like this summary the most:

Musk now says it’s ‘pointless’ to build a Tesla

😁

i meant improving society and strengthen its immune system against threats that would otherwise cause collapses. imperiums cause and collapse/vanish all the time, just try to count the already vanished ones in “known” history, i guess while you are still busy counting the known ones there will be even more “newly found” by archaelogists. while lots of them just vanished without trace, some vanished but just weren’t found yet.

we already know what happens to those in the center. poor ones, poor in their mind, poor in their heart, poor in their outcome.

the ‘empire’ is run to everyone’s expense including the 'empire’s own expense even if they show a whole mess of false evidences that their’re not. they are.

guess making things worse is just his “modus operandi”

But democracy and the voting process brought us Trump! It brought us genocide

the genocide filth that imho lasts >400years now has never been removed in the first place, i’ld guess it wasn’t brought there by voting process, but it wasn’t removed by it either.

“power vacuum” is when all the filth was vacuumed and there is a chance. that chance vanishes when filth starts piling up again and someone else gets into power, creating the need to vacuum again. i’ld rather like it tidy and clean than filth-controlled.

good for you, now plz help others to achieve the same level of security 😉

if you live in an unsafe country, its maybe better for you to flee before it gets even worse.

so then its fully okay for you if its the us thats to be broken then, thanks for admitting it. and after breaking the omlettes eater’s own eggs for him to consume there’s then a chance that no omlettes need to be made any more. a chance of improvement is always better than no chance for it.

but maybe only for emails from outside, not for emails from within protonmail? haven’t read any specs of protonmail yet…

well for e2ee you obviously have to let one e encrypt the data for the other e. (good luck with newsletters then) for usual services kindly asking them to support either s/mime or gpg for outgoing emails, that would at least make them know the wish, but good luck there too.

i think the already mentioned solution with encrypting incoming messages on your side just before mda to your inbox should be the closest possible to what op wants. one would need to check if the message is already encrypted and skip encryption for those.

if you only want the admin of that email (imap) server to not be able to read all emails, maybe placing a separate encrypting server (smtp+encrypt+forward) inbetween outside world and your email imap server could be a solution.

one should have a look into the logfiles too as some mailers might log message subjects and of course sender/recipients along with ip adresses of incoming/outgoing servers which the op might not want to be readable as well (i dont know protonmail that much)

also gpg IMHO allows for sign-then-encrypt hiding the signature within the encrypted data which could be wanted. also one might want to look exactly what parts of the messages contents and its headers are encrypted or plaintext on the server before feeling safe from the threat one wants to be protected from.

but then the admin can still read the mail while it arrives ;-)

nobody changed anything, so why should have anything changed? development does not appear by pure wish or magic, nor by letting time passing by, people have to do it, or it just doesn’t get done.

you’re welcome.

what i’ld suggest… a general rule that i like to always follow is to use a test system for everything new. but that does not need to be a full separate system every time.

lets say you have your mailbox and want to try getting new mails from it using fetchmail. first you can use uidl mechanisms to only fefch every mail once and besides that leave them all on the server, but i like it a bit more secure: create a second email adress/account at your mail providers service only for testing. thus you can do whatever you like to to test the mechanisms only without even touching your real inbox (maybe even fill it up with large emails and look how the system reacts, i once had an email account with a cheap provider that deadlocked the inboxes when full…). then when everything is as you want it, switch the account and password (or create another config file for fetchmail) and your’re done. every change (not only fetchmail things) could go tested this way before going live with the changes. filtering could be done with procmail for example, but when the mda that is called by procmail somehow exits with success when the email really isn’t delivered, then the email might get lost forever depending on the settings of course. so fiddling with new stuff always carries the risk of not fiddling correctly ;-)

have fun !

Its possible to tell your mta (like postfix) to use another mta for all mails, or only some domains etc, so using a third party to play the internet facing service then getting the mails by fetchmail, storing them in a dovecot server is easy. on the sending part you could use your standard email client (i.e. thunderbird on pc or k9-mail on smartphone) to send it to your postfix instance that also sits on the server hosting your dovecot service. the mta there takes the mail and delivers it by rules which could just be using the mta of your freemailer using username/password of your account for all outgoing emails. i am doing this but the “external” mail system are my servers as well, i just don’t want emails to stay too long on VMs in the datacenter where i have no access to the physical disks in case something goes wrong.

a raspberry pi is sufficient for such a aetup (i am using a pi4 currently but for emails only i’ld say a 3 or older would do too), adding a disk via usb makes storage huge and cheap then, i use two usb ssd’s in a raid1 for storage… that server could be only accessible through vpn if you whish, depending on your skills and needs (i mainly use ssl client certificates that are supported by k9mail and thunderbird so it fits seamless to be connected through a haproxy that authenticates these before proxying the plain connection to the pi) clients like thunderbird can offline-store all emails (configure download-or-not per imap folder) making searches easy and quick while my k9 client can search locally or on the server if needed.

maybe adjust maximum mail size of your own mta to exactly match (or slightly less) that of the freemailer you use to prevent surprises of big but later then unsent emails.

its possible to have a nextcloud instance on that same pi that acts as an email web mailer just in case of (i really dont need it, but i’ve set this up anyway). nextcloud is also great for syncing/backup files pictures, contacts notes todo lists and calendar of your phone (where i use davx5 opentasks and foldersync for). there are other webmailers available but installing /using nextcloud is not a too bad idea either ;-)

i suggest also setting up some automatic offsite backup with snapshots of that pi then to cover emails and the setup and its configs ;-)

maybe its that cheap school (or public building) toiletpaper from ages ago that still contained … woodchips?

one example of a program that did multiple things is sfdisk, it used to make the kernel reload the new partition table but that was not its main job, only changing them. the extra functionality moved to blockdev which is nearer to doing such as it also triggers flushing buffers and i think setting read/write status. i am fully ok with that change as it removes code from a program that doesn’t need it to another that already does similar things so that other partitioning programs like gdisk fdisk or parted could go the same way so that maintainers of the reread-partition-table things can concentrate on one solution at one place (in userspace) instead of opening issues at an unknown number of projects that also alter partitioning. the “do one thing” paradigma is good for developers who maintain the code and i pretty much appreciate their work. if you are up to only want one-day-flies that either die or take huge amounts of resources only for keeping them alive (image of a mayfly in an emergency room and a heart-lung machine attached while chirurgs rushing around trying to enlenghten its life a few seconds more) then you are good with monolithic tools that could hardly be maintained and suck allday as no one wants to fix any bugs or cannot without creating new ones due to the tightened dependency hell it has internally.

the point is not a lack of examples doing wrong but where one wants to be heading towards.