Email on a VPS versus Google Workspace (or Microsoft 365)

People buy a VPS to “fix email” the way they buy a truck to “fix commuting.” Sometimes the truck is the right tool. Sometimes they needed a bus pass and a calendar. Running mail on a Contabo VPS is a real architecture: you control the IP, the queue, and the logs. You also control the ways it fails — into spam, into a blocklist, or into a silent port policy. This guide is the decision, not a Postfix tutorial. We will not give you a copy-paste mail server. Those tutorials age into open relays.

What shared hosting already did for you

On cheap shared hosting, the platform sends mail from a pool it has been nursing for years. You get a mailbox UI, a sending cap, and whatever reputation the neighbors left you. For a local shop that sends invoices, appointment reminders, and a contact-form ping, that is often enough. You still should set SPF/DKIM/DMARC if the host documents it — not because you are clever, because Gmail asked. You do not need a VPS for that homework.

Contact-form mail is the usual panic. A form that never arrives is more often a plugin, a spam folder, or a from-address that pretends to be the visitor (which looks like spoofing). It is rarely “we need our own Postfix.” Fix the form to send as you@yourdomain.com through a mailbox you control. If that works, you did not need a server.

What changes on a VPS

You pick the software (a packaged stack like Mailcow, or Postfix plus friends, or a panel’s mail). You set reverse DNS (PTR) so the IP you send from matches the name you claim. You publish SPF, DKIM, and DMARC on the domain at the registrar. You watch logs. You request that Contabo’s PTR and any SMTP policy match what you are doing. Contabo has published mail-on-VPS material and has been known to allow outbound 25 for ordinary use, with abuse limits. Policies change. Read their current SMTP/port documentation. Do not take a 2022 forum post to checkout.

Then you discover the IP might have a history. Recycled IPv4 is normal. If the history is dirty, your carefully authenticated mail still dies. Ticket for a new IP if their process allows it. If you planned to send newsletters, stop: a Contabo VPS is a terrible bulk ESP. Use a mail vendor for campaigns. Use the VPS for transactional mail only if you will treat it like production, not like a hobby port.

Why Workspace or Microsoft 365 is often the calmer inbox

you@yourdomain.com does not require you to run IMAP. Google Workspace and Microsoft 365 exist so a plumber can have a professional address, a spam filter that is someone else’s job, and a phone app that works. You keep the domain at the registrar, you add the MX records they give you, and you do not SSH when mail is slow. The monthly seat costs more than “mail is included on the VPS.” The hours cost less. Shopfront Stack’s parent advice for a local shop is still professional email as a product, not as a daemon.

You can point the website at a VPS and point MX at Google. That split is normal and often correct. The VPS does HTTP. The mail vendor does mail. Do not assume they must live on the same box. Putting them on the same box means a disk-full event takes down both the site and the inbox. That is a bad night.

If you already pay for Workspace and it works, do not migrate mail onto Contabo to “simplify.” You would be trading a product for a project. Simplifying is leaving MX alone when you point the website at a new A record. That is the same lesson as the domain guides: do not touch mail as a side effect.

When self-hosted mail is justified

• You have a reason you cannot use Google or Microsoft (policy, cost at many seats, or a principle you will still fund with time).
• Someone on the team has run mail before and is not learning in production.
• Volume is modest, transactional, and you will not “just add a newsletter.”
• You will monitor bounce and complaint rates, and you will stop sending if you get listed.

Bottom line: buy a Contabo VPS because of an application, not because of an inbox. If mail is the only pain, buy Workspace. If you still self-host mail, treat Contabo’s SMTP policy as a living document, set authentication, keep the website and the MTA from sharing a single point of failure if you can, and do not ask this brochure to be your runbook. We will not impersonate Contabo support when your messages sit in Gmail spam. That ticket is yours, and it is a long one.