Say “corporate email” and many teams jump straight to a Google Workspace subscription. Workspace is a product choice, not the definition of corporate mail. Receivers recognise your brand through MX, SPF, DKIM and DMARC. With those records correct, mail hosted in the EU on your own stack does the same job.
EuroVDC corporate email uses MX securemail.eurovdc.eu (priority 10), a typical SPF v=spf1 mx ip4:45.84.90.12 -all, and zones often on ns1.eurovdc.eu / ns2.eurovdc.eu. Sofia EU infrastructure stays in GDPR geography; a big-cloud logo is not mandatory. Product page: corporate email.
What is mandatory is the DNS record set
Workspace, Microsoft 365, or independent mail — all need correct MX and authentication in your zone. Wrong MX, a broken SPF include chain, a missing DKIM selector, or monitor-only DMARC decide deliverability. Tables: SPF, DKIM, DMARC and deliverability. Nameserver and A/MX/TXT layout: DNS records.
When Workspace makes sense — and when it does not
- Makes sense: Tight Docs/Drive/Meet integration, existing Google identity, deliberate SaaS choice.
- Not required: You mainly need
@company.commailboxes, calendar, and IMAP/webmail. - EU data: Keeping mail in the EU via self-host or a regional provider is still a valid path.
- Cost: Compare per-seat SaaS fees with your DNS + corporate mailbox quota.
Independent corporate setup skeleton
- Stabilize nameservers; point MX at
securemail.eurovdc.eu. - Constrain SPF to
v=spf1 mx ip4:45.84.90.12 -all; add third parties only on purpose. - Publish DKIM from the panel; start DMARC in monitor mode, then harden.
- Create mailboxes: create and manage email accounts; use aliases for roles, keep catch-all off — aliases and catch-all.
- Take IMAP/SMTP settings from documentation; a working Gmail forward is not an architecture.
Assumptions that fail
Believing you cannot have “real” mail without a Google account; expecting PHP mail() from web hosting to act corporate; leaving two half-configured MX/SPF sets live. Pick one authoritative mail path, lock DNS to it, retire the rest.
FAQ
Can we reach Gmail recipients without Workspace?
Yes. Delivery into Gmail depends on your authentication and reputation, not on whether you buy Workspace.
Is self-hosted EU mail still valid?
Yes — if you patch, back up, monitor, and keep DNS disciplined. A regional corporate product like EuroVDC runs that for you.
Can I trial without switching MX to Workspace?
Subdomain or planned dual-delivery only. Two half-live MX sets lose mail. Document a single cutover step.
What if we need calendar and file sharing?
Mail and groupware can be separate choices. Keeping mail in the EU and files elsewhere is possible; write the policy clearly.
Must SPF include Google?
Only if you send via Google infrastructure. On EuroVDC securemail the typical record is mx plus the published IPv4 — do not paste random includes.
