![]() ![]()
Until SSH is set up properly on your machine, consider that any password sent through is compromised. The NSA is known to collect SSH keys as systems get set up, so be careful. 4) The first (and I mean very first) thing you do the first time you log in is make sure SSH is set up properly.Plus, as a bonus, almost every tutorial for Ubuntu, Mint, etc will also work on it. They may dither themselves into insensibility sometimes, but that just makes it stronger if you ask me. #Surgemail disable reverse dns software#95% of all desktop Linux is based on Debian, vanilla Debian is server friendly, Debian is conservative (which is what you want for a server) and they take software freedom seriously. I pay $10/mo for prod and $5/mo for my testing server. When you are using root to first set it up, create an admin directory and religiously duplicate every config file you edit into that admin directory so you can duplicate everything you do onto prod when you set it up. When you set them up, set up testing first. You will want your own DNS server for when you get into SPF, DKIM, DMARC, and so forth. This also lets you do your own DNS and gives you a primary and backup DNS server. This lets you try everything out (including upgrades) on the test platform before rolling out on prod. One will be the production, the other will be the test. Whatever solution you get for hosting, get two. Make sure your login to your VPS host is extremely secure. #Surgemail disable reverse dns professional#The one I use is CACloud, and I have found them to be extremely professional and very reasonably priced. This is great for people physically located in the USA too, since it offers you better privacy protection, and good connectivity. Being Canadian, I chose a home-based solution. No matter where you live, I'd highly recommend not even thinking about getting one physically located in the USA. I recommend finding a good KVM VPS (Virtual Private Server) hosting service. 1) First thing to think about is hosting. #Surgemail disable reverse dns plus#But I will offer some points of advice plus all the documentation I usd to set up mine: I'm not going to give total step-by-step instructions, because that's long and complicated. And, as a bonus, it gives me a "server" for SyncThing, which means I have my own "DropBox"-like solution that I control. It also lets me run a couple domains of WordPress too. It's end-to-end secure with excellent encryption that I can trust. I have multi-domain virtual mail hosting configurable with a few clicks through PostfixAdmin. When I set mine up it took me a week or so of initial pain, and it was a lot of work I won't lie, but now I have a server I know inside and out and has been reliable as a Clydesdale. If you really want to get a good mail server running, the best way to do it is to learn and do it yourself. But the problem with those is that you get people who know enough to apply a turn key solution without knowing enough about the workings to handle issues that come along. Mailinabox is a turn key solution, sort of, and there is nothing really wrong with that. How would you host your own email server? Leave your own suggestions in the comments. Any tips/tricks/pointers would be great appreciated!Ī lot's changed in 20 years - but for such a basic form of online communication, is it still possible to roll your own? Or are we trapped in a world where private conversations about valuing open source software take place inside Google's proprietary Gmail client. So, I am reaching out to this great community to find out if there are any good tutorials on modern-day best-practices for self hosting an email server. It was easy back then - there was much less SPAM and self-hosted email servers didn't have to jump through hoops to make sure that they weren't blacklisted as senders. The problem is, I haven't run my own email server since the 90s. ![]() The first step will be to build/setup/run my own email server for my vanity domain. Long-time Slashdot reader whh3 wants to live differently - and to model a different set values:Īfter reading the recent Doc Searls article in Linux Journal, I realized that I need to get back to my roots. "It has become too easy to take Linux and FOSS for granted," warns a Linux Journal editorial by Doc Searls, complaining, for example, that today "We collaborate inside proprietary environments, such as Slack and Google Hangouts." ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |