Installing a mail server on a VPS takes an afternoon. Getting your invoices into a client's inbox takes months of DNS work, IP reputation management and quiet monitoring. Most businesses discover the difference the day a quote lands in a spam folder and nobody notices for a week. This guide explains what hosting your own email on an NVMe VPS really involves, which SPF, DKIM and DMARC records you have to publish, and when a managed mailbox service is simply the better trade-off.
What "hosting email on a VPS" actually means
An NVMe VPS is a KVM virtual machine you control: root access, a management panel, a dedicated IPv4 address. Open Vista runs the infrastructure — hypervisor, network, storage, DDoS protection, 24/7 supervision — under a 99.9% SLA that covers infrastructure. Everything above that layer is yours, and that is exactly where deliverability is decided.
- The transport software. A mail transfer agent such as Postfix or Exim has to be installed, hardened, patched and watched: queue depth, rejections, authentication attempts.
- The mailboxes. IMAP storage, webmail, mobile sync and spam filtering are separate pieces you must size and maintain.
- DNS. SPF, DKIM, DMARC and the reverse record determine how receiving servers treat every message you send.
- Reputation. A new IP address has no history. You warm it up, watch complaints and fix problems fast.
The boundary is clean: the provider keeps the machine and the network up, not your messages out of the spam folder.
SPF, DKIM and DMARC: three records that decide where your mail lands
When your server hands a message to the recipient's server, that server first asks whether it can trust you. Three DNS records answer the question, and they only work together. One of them misconfigured is enough to send a perfectly legitimate invoice to the spam folder.
SPF: who is allowed to send for your domain?
The SPF record is a TXT field at the domain root listing the servers authorized to send on your behalf. If your VPS is the only sender, the list stays short. Watch the ten-DNS-lookup limit the standard imposes: chained includes blow through it quickly, and an oversized SPF record is a broken SPF record.
v=spf1 ip4:YOUR_IPV4 -all
The final -all is a decision, not a formality: it rejects any sender you did not list. A temporary ~all leaves room for doubt but does nothing for your reputation.
DKIM: the signature that proves nothing was altered
Your server signs each outgoing message with a private key; the matching public key is published in a TXT record under a selector, for example mail._domainkey.yourdomain.com. The recipient recomputes the signature and checks that no relay modified the message. Key rotation and selector choice are already operations work.
DMARC: the policy and the reports
DMARC replaces neither SPF nor DKIM: it tells the recipient what to do when both fail, and sends you aggregate reports about who is sending as you. Start at p=none to observe real traffic, then tighten to quarantine and reject once every legitimate source is known.
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com; adkim=s; aspf=s
The reverse record and alignment
The PTR record ties your IPv4 address to a hostname, and many receiving servers penalize a missing or generic PTR. Every Open Vista VPS plan includes a dedicated IPv4; you request the PTR from the provider, and the name has to match the domain you send from, or DMARC alignment breaks and the first three records stop helping.
IP reputation builds slowly and disappears fast
A spam filter does not read your message the way a person does: it looks at where the message came from first. A dedicated, clean, stable IP address is therefore the foundation of any self-hosted mail setup. It also has no history on day one, and that emptiness is the problem: large mailbox providers are suspicious of unknown addresses that suddenly send hundreds of messages.
- Volume. A gradual ramp over several weeks beats a mass send on day one.
- Complaints. The "report spam" button carries real weight; clean opt-in lists and a visible unsubscribe link are not optional.
- Blocklists. A listing can be checked and removed; ignoring one means sending into a void.
- Consistency. PTR, SPF, DKIM and DMARC must tell the same story, or the message looks forged.
This is continuous work with no end date. A few invoices a week are manageable; regular campaigns and application notifications demand real expertise.
Three realistic options for a business email address
The question is not "VPS or no VPS" but "who owns deliverability". All three approaches below are defensible; they simply cost different amounts of energy.
| Criterion | Mail on your VPS | Managed mail (OX App Suite) | Shared cPanel |
|---|---|---|---|
| Mail server | Installed and maintained by you | Run by the provider | Run by the host |
| DNS and reputation | Entirely on you | Set up with you, filtered upstream | Partly shared |
| Access and control | Root, logs, custom rules | Mailboxes, calendar, sharing, webmail | Standard mailboxes, few settings |
| Backups | To design and test | Included in the service | Depends on the plan |
| Real monthly effort | Several hours, especially early on | A few minutes | Close to none |
| Best fit for | A very specific business need | SMBs, freelancers, teams | A simple brochure site |
Managed mail rides on trust infrastructure that already exists, with spam filtering, archiving and support: that is the trade-off most SMBs pick. The VPS keeps its value when an application, a helpdesk or a transactional sending gateway has to live on the same machine and you want full control over the logs.
Which VPS if you insist on running your own mail
If you accept the operational burden, size RAM before anything else: spam filtering, IMAP indexes and the mail database eat far more memory than network traffic does. NVMe storage matters too, because mailboxes only grow.
| Plan | vCPU | RAM | NVMe | USD/month | MAD excl. tax |
|---|---|---|---|---|---|
| VPS-1G Démarrage | 1 | 1 GB | 30 GB | 9.99 | 94.48 |
| VPS-2G Business | 1 | 2 GB | 40 GB | 19.99 | 189.06 |
| VPS-3G Performance | 2 | 3 GB | 50 GB | 34.99 | 330.93 |
| VPS-4G Avancé | 2 | 4 GB | 80 GB | 39.99 | 378.22 |
| VPS-5G Ultra | 3 | 5 GB | 100 GB | 49.99 | 472.80 |
Every plan includes a dedicated IPv4, unlimited bandwidth, root access, the management panel, automatic backups, a firewall with DDoS protection, 24/7 supervision, six-day-a-week support, a 99.9% infrastructure SLA and delivery in under 15 minutes. Upgrading to a bigger plan needs no painful migration.
One piece of context: production runs in New York today, and a Rabat facility is announced but not open yet. For email, latency barely matters because SMTP is asynchronous; it does matter if the same machine also serves an interactive application.
FAQ
Can I run mail on the cheapest VPS plan?
Technically yes: VPS-1G Démarrage at $9.99 a month gives you 1 vCPU, 1 GB of RAM and 30 GB of NVMe. In practice, 1 GB leaves little room for spam filtering, an IMAP engine and the operating system. It is a reasonable lab for a handful of mailboxes, not an enterprise mail server.
Does the 99.9% SLA cover email delivery?
No, and it is worth being blunt about it: the SLA covers infrastructure — the availability of the virtual machine and the network. It does not guarantee deliverability, inbox placement or the reputation of your IP address, which depend on your DNS configuration and sending practices.
Do I need a dedicated IPv4 and a PTR record?
Yes, both. Every VPS plan includes a dedicated IPv4, so you are not sharing reputation with other customers. The PTR must be requested from the provider and should point to a name consistent with your sending domain; without it, many receiving servers apply an immediate penalty.
Can I start on a VPS and move to managed mail later?
Yes, if you prepare the move: lower the TTL on the records involved, export mailboxes in a standard format, keep the same SPF and DKIM during the transition and change the MX last. Going the other way is harder, because IP reputation starts over from zero.
The sensible decision: keep mail off the web server
For most SMBs, business email is not an experiment: it carries quotes, invoices and follow-ups. Handing it to a managed professional email service removes the DNS burden and the late-night incidents; keeping the website and applications on an NVMe VPS preserves speed and control. Think about your domain name too, since it carries your sending identity. If you are torn between the two models, tell us your sending volume and constraints and we will tell you honestly which one holds up over time.