How do you get email on your own domain?
You use the email hosting included with your web hosting plan, or sign up for a dedicated email service, and point a few DNS records at whichever one you choose. Neither option requires you to run your own mail server, and for almost everyone reading this, that is exactly the right choice. Email at your domain, like [email protected], is a service someone else provides. You are just renting a mailbox, the same way you rent your domain name itself.
I want to be upfront about the trap this post is named for: it is entirely possible to install mail server software on a VPS, and plenty of tutorials will walk you through it. I would not recommend it to a beginner, and I will explain exactly why before getting into the parts that actually work well.
Why is self-hosting a mail server such a common beginner trap?
Because the software is only half the job, and it is the easy half. Installing mail server software on a VPS is a solvable technical task. Getting the email that software sends to actually land in someone's inbox instead of their spam folder is a completely different and much harder problem, one that has little to do with your server configuration and everything to do with reputation.
Large email providers, the ones most of your recipients use, are cautious by design about mail arriving from servers they have never seen before. A brand-new VPS sending its first emails has no track record at all, so those emails are treated with suspicion by default. Building a trusted sending reputation from nothing takes sustained, careful effort, and even people who do it well sometimes fight spam filters for months.
What is deliverability, and why does it matter more than the mail server itself?
Deliverability is simply whether your email actually arrives where you sent it, in the inbox rather than spam or nowhere at all. It is the entire point of sending email, and it is determined mostly by factors outside the mail server software itself: your sending domain's history, whether your DNS records correctly authorize your sending source, and how recipients and spam filters have treated mail from you before.
This is why the practical advice here is not "avoid running a mail server because it is hard to configure." The software is not the hard part. Deliverability is, and it is a problem dedicated email providers and hosting companies have spent years solving at scale, in a way one person running one VPS realistically cannot replicate quickly.
What are SPF and DKIM in plain English?
These are two DNS records, similar in spirit to the ones covered in our domains and DNS guide, that help receiving mail servers trust your outgoing email. SPF, sender policy framework, lists which servers are allowed to send mail claiming to be from your domain, so a receiving server can check an incoming message against that list and flag anything that does not match. Think of it as a guest list for who is allowed to speak on your domain's behalf.
DKIM, domain keys identified mail, adds a digital signature to each outgoing message that proves it truly came from you and was not altered along the way. Together, SPF and DKIM are two of the strongest signals a receiving server uses to decide whether your email is trustworthy, and getting both set up correctly meaningfully improves the odds your messages land where you want them.
What is the easiest way to actually set this up?
Sign up for the email hosting included with your web host, or a dedicated email provider if you want more mailboxes or features than your host offers. Either way, you will be handed a short list of DNS records, usually including SPF and DKIM, to add at your domain's DNS settings. That step takes a few minutes and looks a lot like the A record work covered in our guide on connecting a domain to a VPS, just with different record types.
From there, the provider handles the actual sending and receiving infrastructure, spam filtering, and the deliverability reputation that would otherwise be your problem to build from scratch.
What is the difference between hosting-included email and a dedicated mail service?
Hosting-included email, the kind bundled with a shared hosting plan, is usually the simplest and cheapest path if you want a small number of mailboxes at your domain, and setup is often close to automatic. A dedicated email service is worth considering if you need more mailboxes, better spam filtering, or features like shared calendars and larger storage, and are willing to pay a bit more or manage a separate account for it. Neither option asks you to run or maintain a mail server yourself, which is the point.
What if you already tried self-hosting and it is not working?
Do not treat it as a personal failure, it is the expected outcome for almost everyone who tries. Move your domain's email to a hosting-included plan or dedicated provider, update your DNS records to point at the new service, and retire the self-hosted mail server. Your domain and any existing email addresses stay yours through that switch, only where the mail is actually processed changes. It is a clean fix, not a consolation.
Does this mean a VPS is bad for everything, not just email?
No, and it is worth being clear about that, since I run most of my own projects on a VPS and recommend it often on this site. Websites, automation tools, and small apps do not carry the same reputation problem email does, because visitors reach them by you handing out a link or domain, not by a third-party spam filter deciding whether to trust an unfamiliar sending server. Email is the one category where a fresh, self-managed server starts at a real disadvantage compared to an established provider, simply because of how spam filtering works industry-wide.
So the honest takeaway is not "avoid running your own server." It is "pick the right tool for each specific job." A VPS is a great tool for hosting your site, running automation tools like n8n, or serving several projects at once. Email is the one piece worth carving out and handing to a specialist provider instead, and doing that costs you very little in exchange for a lot fewer headaches.
Next step: once email is sorted, the rest of your domain setup usually falls into place quickly. Our learn AI hub has more beginner guides on domains, hosting, and getting the basics right the first time.
