Interests: News, Finance, Computer, Science, Tech, and Living

  • 0 Posts
  • 6 Comments
Joined 3 years ago
cake
Cake day: June 13th, 2023

help-circle


  • Just to emphasize it is the reputation problem and getting common mail providers the accept. You’ll need to get a well known domain like a .net or .com domain. You probably need to have a web site too on the domain. Then let that stuff age. You’ll also need to get a static IP for the VPS your using that has a good reputation and your hosting provider will have to allow you to send email which means you’ll have to talk with them to make sure everything it setup. You’ll also probably want certs both for the website, and for your SMTP server. Then there are SPF, DKIM, DMARK, and DNS configuration you’ll have to make too. Optional other configs like MTA-STS, or DANE. Just a lot of detail. Once your setup, there are testing sites you can go to test or SMTP server.

    Another issue is you want email to be full time. So I think that probably means 2 incoming mail servers on two different VPS systems maybe in two different data centers. Then you need IMAP, and maybe a webmail system. I guess these last two could be one one of the VPS systems hosting one of the SMTP servers. Lot of components.

    I don’t actually using my own VPS based mail system for my main email addresses. Instead we use a shared hosting plan and our own domain instead. You might want to look at is Namecheap CPanel Email that Comes with their Stellar Hosting plan. That is what we use. You can use up to 30 addresses on their base plan and maybe unlimited on the next level up. It is less then $100 per year after you add all you need, the hosting plan, a domain, and certs (maybe more in the $60 range?). The advantage of this, the hosting provider takes care of the infrastructure, and it is cheaper and lest time consuming then two VPS systems and all the work to maintain them.

    About getting other providers to accept your mail, I’ve found Yahoo and the domains they serve to be one of the worst offenders.




  • Thanks, I did not see that before.

    Other interesting thing is that about:config is disabled on mobile except maybe nightly. Wonder why?

    The other advantage of Brave is that it is more secure out of the box. From privacy point of view that should be better at blending in to the crowd depending on user base size. In Firefox I usually add an extension and configure it and some about:config settings. Somewhat minimal but probably quite unique.


  • I did not find any justification of why they arbitrarily did not considered Gecko browsers in privacyguides. They just made that statement. I am not surprised that certain chromium browsers are more secure simply because Google has a bigger budget, but I did not see any justification for it. Then again the EFF will say that Tor Browser is better then Brave so we can argue about these minor points forever.

    Then again none of that minor stuff matters to me. I care more about the goals of the organizations themselves and I am not convinced that any of the Chromium browsers take us down a sane path. So I will be staying with Firefox thank you very much.