The sweet spot for having control over your email while simultaneously minimizing unforseen headaches is to simply own your domain name and point the MX record to whatever hosting provider you want instead of self-hosting a server at home. Same philosophy for exposing a your personal blog of html files or content like mp4 videos. The sweet spot is to focus on buying a domain name you control. Then let Amazon S3, or C…
"The sweet spot for having control over your email while simultaneously minimizing unforseen headaches is to simply own your domain name" You would think. The issue no one seems to think about is that you need to make sure to pay for the domain for the duration of your life(at least). Otherwise, as soon as you lose your domain you lose ownership of your email. Any one that has control of the domain has control of you…
After self-hosting my email for twenty-three years I have thrown in the towel
241–250 of 744 posts
Re: After self-hosting my email for twenty-three years I have thrown in the towel
#242Earlier quoted context omitted.
I guess a lawyer might know a thing or two about confidential messages.
I think you’d be very surprised at how much lawyers don’t know or care about any of that. They store stuff in the cloud without ever having heard of the Third Party Doctrine (which allows the US government warrantless access to those documents).
Re: After self-hosting my email for twenty-three years I have thrown in the towel
#243It was a huge mistake for email receivers to take on the cost of filtering spam. Of course given the evolution of the internet and email it is easy to see how that mistake happened. Nobody had a crystal ball. But the only solution here is to raise the cost of sending email to the point where spam is no longer profitable. It seems like one solution is to bcrypt hash (or some similarly expensive algorithm) the email an…
This indeed looks like a good direction. A decade ago Freenet (not sure if it still exists?) had a problem with spam on its equivalent of USENET. It was pretty bad, until they changed the protocol so that it's the sending node that keeps the message, which is then pulled (or not) by the recipients. It made a lot of sense to me: I'm the one sending you the message, I want you to see it, while you don't even know wheth…
Re: After self-hosting my email for twenty-three years I have thrown in the towel
#244Earlier quoted context omitted.
Trust (by way of VMC) is the whole point of BIMI; it’s what’s in all the marketing copy: The fact that nobody else can send mail with your logo. If you merely wanted to send e-mail with your icon on it, that already existed: the X-Face header has been around for decades.
Absolutely not, BIMI is a way to provide brand identity for recognition/marketing purposes. Trust or security is not the standard's goal. Being able to trust the logo is an optional extra. Also nobody really uses X-Face, it's irrelevant.
1. BIMI logos are in color.
oh yeah, and:
2. BIMI logos are inherently a tracking pixel so the sender can see when readers read the mail.
Re: After self-hosting my email for twenty-three years I have thrown in the towel
#245Re: After self-hosting my email for twenty-three years I have thrown in the towel
#246Earlier quoted context omitted.
Absolutely not, BIMI is a way to provide brand identity for recognition/marketing purposes. Trust or security is not the standard's goal. Being able to trust the logo is an optional extra. Also nobody really uses X-Face, it's irrelevant.
You’re talking nonsense. What is the improvement of BIMI (without VMC) over X-Face? The only things I can think of are: 1. BIMI logos are in color. oh yeah, and: 2. BIMI logos are inherently a tracking pixel so the sender can see when readers read the mail.
The next section also literally says "This document does not cover the different verification and reputation mechanisms available, but BIMI relies upon them to be in deployed in order to control abuse." It's not a standard meant for establishing trust, it does not mandate requiring a VMC.
Re: After self-hosting my email for twenty-three years I have thrown in the towel
#247Earlier quoted context omitted.
There is also a happy medium. Host your own MX servers but use someone else's SMTP servers. You have complete control over the incoming mail but dodge the filters by using the established business for sending mail.
> Host your own MX servers but use someone else's SMTP servers. Yes. My outgoing email goes out via Sonic's SMTP server, with the SPF records to allow it to have a source address of my own domain. Incoming email goes to my own domains and gets forwarded. This seems to be trouble-free. The domain is on a cheap shared hosting account. I'm not running a server. I own the domain, and not though the hosting company, so I…
Re: After self-hosting my email for twenty-three years I have thrown in the towel
#248The sweet spot for having control over your email while simultaneously minimizing unforseen headaches is to simply own your domain name and point the MX record to whatever hosting provider you want instead of self-hosting a server at home. Same philosophy for exposing a your personal blog of html files or content like mp4 videos. The sweet spot is to focus on buying a domain name you control. Then let Amazon S3, or C…
There is also a happy medium. Host your own MX servers but use someone else's SMTP servers. You have complete control over the incoming mail but dodge the filters by using the established business for sending mail.
Re: After self-hosting my email for twenty-three years I have thrown in the towel
#249Honestly wish there were a mode where you pay me $x to send me email and I can sort by spend.
The name evades me, but this was a thing a few years back. IIRC, it was the equivalent of what a stamp for an envelope would cost, and the recipient got a chunk, as did the service provider. Will try and find the name for you, but AFAIK, it's no longer doing business.
Re: After self-hosting my email for twenty-three years I have thrown in the towel
#250Reading the comments here makes me incredibly sad. Every answer that tells me to use a provider misses the point. The Internet was created so that there could be many independent nodes, not so that everybody has to rely on one of several blessed providers. I should be able to run my own E-mail.
The real problem is lack of incentives. The big corps do not care about e-mail. It doesn't make money and isn't easily controllable. You can't turn it into a walled garden and lock users in. So, it gets minimal attention, and only defensive measures are developed.
Either we solve the spam problem, or things will get worse. The big tech corps won't solve it for us.