Why Salieno Core Ships Without a Built-In Mail Server

The Email Problem Every Small Host Faces#

If you've ever run shared hosting, you know the pattern: a customer's email lands in spam, they open a ticket, you spend an hour digging through Postfix logs and SPF records, and the root cause is that another tenant on the same IP got flagged by Gmail three weeks ago. Email is the single biggest support burden in shared hosting — and the least profitable.

Salieno Core ships without a built-in mail server. That's not an oversight or a missing feature. It's a deliberate architectural choice, and one that reflects where the hosting industry is heading.

Email Hosting Is a Business, Not a Feature#

The economics are straightforward. A typical shared hosting account might generate $5–15/month. Email deliverability support for that same account can easily consume 20–30 minutes of staff time per incident. At a blended support cost of $25–40/hour (even for offshore teams), a single spam complaint can erase the margin on that customer for months.

Meanwhile, dedicated email providers — Google Workspace, Microsoft 365, Zoho Mail, Fastmail, MXroute — have entire teams focused on IP reputation, feedback loops, DKIM rotation, and DMARC enforcement. They operate at a scale where maintaining sender reputation across millions of domains is a core competency, not an afterthought.

For a reseller or indie host, trying to compete with that is a losing proposition.

The Deliverability Arms Race#

In 2024 and 2025, the major inbox providers tightened their authentication requirements significantly. Google and Yahoo now enforce DMARC, DKIM, and SPF alignment for any sender delivering more than 5,000 messages per day to their platforms — but even below that threshold, messages without proper alignment are increasingly filtered.

Running your own mail stack means you're responsible for:

• Maintaining clean IP addresses (no blacklist history)
• Configuring SPF, DKIM, and DMARC records correctly for every domain
• Handling feedback loops with Gmail, Outlook, Yahoo, and dozens of smaller providers
• Monitoring bounce rates and complaint thresholds
• Managing TLS certificates for SMTP
• Keeping the mail server patched against vulnerabilities (Postfix, Exim, and Dovecot all have regular CVEs)

Each of these is a part-time job. Combined, they're a full-time one — and most resellers don't have the volume to justify it.

What Salieno Core Does Instead#

Rather than bundling a mail server that becomes your problem to maintain, Salieno Core manages the DNS side of email authentication. When a customer's domain is set up, the system generates the correct MX, SPF, DKIM, and DMARC records pointing to whatever external mail provider the host or customer chooses.

This means:

• DNS records are correct by default. No manual TXT record entry, no typos that silently break deliverability.
• Customers can choose their provider. Some hosts bundle Zoho (free for up to 5 users), others resell Google Workspace at a markup, and some use MXroute for budget-conscious clients. The control panel supports any of them.
• Support burden drops dramatically. When email is handled by a dedicated provider, deliverability issues become that provider's responsibility. Your team handles billing and account provisioning, not SMTP debugging.

The DNS manager in Salieno Core was built from scratch partly for this reason — off-the-shelf DNS solutions don't integrate cleanly with the kind of automated record provisioning that makes external email seamless.

The Self-Hosted Exception#

There are legitimate reasons to run your own mail server. Agencies managing client communications on-premise, hosts in regulated industries with data-sovereignty requirements, or operators serving markets where major providers don't have local presence — all of these cases exist.

For those scenarios, Salieno Core's plugin architecture allows adding a mail server module. Postfix and Dovecot can run alongside the platform, and the DNS manager will generate the appropriate authentication records automatically. But it's an opt-in choice, not a default that creates liability for every tenant on the server.

The key distinction is that running mail becomes a conscious decision with known trade-offs, rather than a hidden cost baked into every shared hosting account.

What This Means for Your Business#

If you're a reseller currently running bundled email, consider tracking your email-related support tickets for 30 days. Categorize them: spam complaints, delivery failures, configuration questions, quota issues. Multiply the count by your average handling time, then by your effective hourly cost.

The number is usually sobering.

Many hosts who've moved to external email report a 40–60% reduction in support volume. Some pass the cost of a basic email plan ($1–3/user/month) to the customer; others absorb it as a margin play against the support savings. Either way, the math works out favorably compared to maintaining your own SMTP infrastructure.

A Principle, Not a Limitation#

The decision to exclude a built-in mail server follows the same logic behind Salieno Core's other architectural choices: don't bundle what you can't operate better than a dedicated provider. The billing engine, the control panel, the DNS manager, the job queue — these are core to what a hosting platform needs to do. Email delivery, like domain registration or CDN services, is better handled by specialists.

Your customers get better deliverability. Your support team gets fewer tickets. Your infrastructure gets simpler. That's the kind of trade-off worth making deliberately.