Mail.Baby Review 2026: Cheap SMTP Service Pros & Cons

If you’re running a self-hosted application on a VPS (whether that’s a Hetzner box, a Hostinger VPS, or your own Docker containers home server) and need a cheap SMTP service for outbound email, this Mail.Baby review covers what you need to know. Mail.Baby is a budget transactional email service by Interserver that costs $1/month plus $0.20 per 1,000 emails. Since my original 2023 review, the service has added several useful features.

The biggest change: Mail.Baby added a new SPF verification method in December 2025 that eliminates the need to expose your server’s IP address in DNS. That was the main security concern with this service, and it’s now resolved.

I’ve been using Mail.Baby across multiple servers for transactional email and bulk sends. Here’s what I look for in an email-sending service:

If you’re running applications on a VPS and want to set up outbound email with Postfix, Mail.Baby works well as an external SMTP relay. Whether you’re choosing between VPS providers or already have a server running, Mail.Baby connects the same way regardless of hosting.

What is Mail.Baby?

Mail.Baby is a budget outbound SMTP relay service operated by Interserver. It sits between your server or application and the recipient’s mail server, handling deliverability, IP reputation, and spam filtering on your behalf.

You can send both transactional emails (password resets, order confirmations, monitoring alerts) and marketing emails (newsletters, campaigns) through the same service. Not all SMTP providers allow both. Many restrict or charge extra for marketing sends.

Since May 2024, Mail.Baby runs all email infrastructure in-house. Previously they used MailChannels as a backend, but moving everything in-house gives them full control over their IP reputation and delivery pipeline. This changed how consistently emails get delivered.

Mail.Baby pricing

Mail.Baby charges a $1/month base fee plus $0.20 per 1,000 emails sent. The $1 monthly fee covers up to 5,000 emails, so if you send fewer than 5,000 emails per month, your total cost is just $1.

Worked examples:

There’s no free tier, unlike Amazon SES (which offers 3,000 free message charges per month for the first 12 months). But the base cost is low enough that it barely matters for small senders.

SPF configuration: two setup options

This is the section that changed the most since the original review. Previously, Mail.Baby required you to add your server’s IP address to the SPF record, which exposed it publicly in DNS. That was a real security concern, especially if you used Cloudflare to proxy your server.

As of December 15, 2025, Mail.Baby offers an alternative: a TXT verification record that eliminates the IP exposure entirely.

What is SPF?

SPF (Sender Policy Framework) is a DNS record that tells receiving mail servers which servers are authorized to send email on behalf of your domain. Mail.Baby checks your SPF record to verify your server is authorized before relaying your emails.

Here are both configuration methods:

v=spf1 ip4:YOUR.SERVER.IP include:spf-c.mailbaby.net -all

_mailbaby.yourdomain.com  IN  TXT  "v=1 user=mbXXXXX"

v=spf1 include:spf-c.mailbaby.net -all

The new TXT record method removed the single biggest objection to using Mail.Baby. If you’re running a server behind Cloudflare and care about securing your VPS, Option B is the way to go.

Sending limits and deliverability

Hourly sending cap

Mail.Baby enforces a limit of 6,000 emails per hour per email address, not per account. If you have multiple sender addresses configured, each one gets its own 6,000/hour quota.

The critical detail: emails that exceed the 6,000/hour limit are discarded, not queued. Unlike some competitors (Mailchimp Transactional Email, for example, queues excess sends), Mail.Baby simply drops them. You’ll get a rejection, but the email is gone.

This matters if you’re doing bulk sends. If you need to send 20,000 emails, you’ll need to spread them across multiple hours and potentially multiple sender addresses. Tools like monitoring scripts that send email alerts typically won’t hit this limit, but newsletter tools or batch processors might.

New user filter / warming period

New Mail.Baby accounts start with a “New User Filter” that applies stricter outbound filtering. This means your first batch of emails may get flagged or blocked more aggressively than established accounts.

Gradual ramp-up is the way to go. Start with small volumes of legitimate transactional email, build your sending reputation, and then scale up. Don’t sign up and immediately blast 5,000 marketing emails.

Deliverability performance

In my experience and based on community feedback across LowEndTalk and Reddit, deliverability is solid. The move to an in-house relay in May 2024 gave Mail.Baby full control over IP reputation management.

Recent security improvements include:

• AI-powered phishing detection (January 2026), scans outbound emails for phishing patterns
• “Rattle Trap” reverse spam traps (December 2025), identifies spam sources proactively
• Batched logging speed boosts (April 2026), infrastructure upgrade for faster processing

These additions show the team is actively working on the platform.

Security and email authentication

Connection security (ports and TLS)

Mail.Baby supports the following connection options:

STARTTLS is used by default. If your server doesn’t support TLS, you can connect insecurely, but that’s not recommended. All SMTP details and credentials are available in the Mail.Baby control panel after signup.

DKIM and DMARC alignment

For best deliverability to Gmail, Yahoo, and other major providers, you need proper email alignment. This means your “Header From” address (what the recipient sees) should match your “Envelope From” address (what SPF/DKIM checks use).

Mail.Baby’s getting-started guide covers DKIM signing and DMARC policy setup. If you’re sending from multiple domains, each domain needs its own DKIM key and DMARC record. This is standard for any SMTP relay, not specific to Mail.Baby.

Spam filtering and bounce handling

Mail.Baby scans outbound email for spam content. If your server gets compromised and starts sending spam, Mail.Baby will block the outgoing messages. This protects both your reputation and theirs.

Bounce codes are now documented, which helps interpret delivery failures. Common codes cover SPF failures, compromised account detection, and bot form submissions. Check Mail.Baby’s bounce message guide for details.

REST API and WordPress integration

Two major additions since the original review: a REST API for developers and a WordPress plugin for non-technical users.

Using the Mail.Baby REST API

Mail.Baby offers a full REST API (v1.5.0) documented at api.mailbaby.net. The API supports:

• Simple send, basic email with to, from, subject, and body
• Advanced send, CC, BCC, attachments, custom headers
• Raw send, pre-built RFC 822 message format
• Delivery logs, query send history and status
• Block management, manage blocked recipients
• Deny rules, configure outbound filtering

The API has an OpenAPI spec available, and sample clients exist in multiple languages on GitHub. If you’re building a custom application that sends email, the API is cleaner than configuring SMTP credentials.

WordPress setup with Mail Baby SMTP plugin

The official “Mail Baby SMTP” WordPress plugin has 600+ active installations and is currently at version 3.2.13 (tested up to WordPress 6.9.4).

The plugin supports multiple mailers: Mail.Baby, Sendinblue, Mailgun, SendGrid, Gmail, and SMTP.com. Install it from the WordPress plugin directory, enter your Mail.Baby credentials, and it handles SMTP configuration automatically.

If you’re running WordPress and want to explore other SMTP options, see our guide on sending emails in WordPress using Zoho SMTP with FluentSMTP. And if you’re managing WordPress sites, having reliable backup plugins is just as important as reliable email delivery.

Setup and registration

How to sign up

1. Go to Interserver and create an account
2. Navigate to Mail → Order in the control panel
3. Select the Mail.Baby email package

After ordering, your SMTP credentials and connection details appear in the control panel. The setup is straightforward, no complex onboarding process.

If you need to configure Postfix to use Mail.Baby as an external SMTP server, we have a detailed guide covering that setup. For managing your server alongside Mail.Baby, check our comparison of self-hosted server panels.

Control panel setup guides

Mail.Baby provides official setup guides for popular control panels:

• cPanel, Setup guide
• DirectAdmin, Setup guide
• Postfix / Plesk, Setup guide
• Mailcow, Setup guide

A separate Mail.Baby control panel (independent from Interserver’s main dashboard) is in development. The current interface works but is cluttered with unrelated Interserver services.

Mail.Baby pros

Mail.Baby cons

• No queuing for excess emails, emails beyond 6,000/hour per address are lost, not queued for the next hour.
• Interserver-branded dashboard, the control panel is cluttered with unrelated Interserver hosting services. A separate Mail.Baby panel is coming but not yet available.
• New user filter, stricter outbound filtering on new accounts means you can’t blast large volumes on day one.
• False positives in spam filtering, community reports occasional legitimate emails getting flagged. Rejected emails are still billed.
• No free tier, unlike Amazon SES which offers 3,000 free message charges per month for the first 12 months.

Mail.Baby vs alternatives

Here’s how Mail.Baby compares to other popular SMTP services:

Amazon SES is the closest competitor on price. New AWS accounts get 3,000 free message charges per month for the first 12 months. After that, or if you’re not on EC2, you pay $0.10/1,000 emails. Still cheap, but SES requires more setup and AWS knowledge.

MXroute offers flat pricing with no per-email charges, which makes it attractive for high-volume senders. But the base price starts at $5/month.

Mailgun and SendGrid provide polished dashboards, better analytics, and more developer tooling. You’re paying for the experience. They make sense when email is a core part of your product, not just a utility.

Mailchimp Transactional Email (formerly Mandrill) requires a Mailchimp account and is the most expensive option. It’s designed for Mailchimp users who need transactional sends alongside their marketing platform.

If you’re looking for another SMTP relay option, also consider setting up SMTP relay with ZeptoMail as an alternative.

Should you use Mail.Baby?

Mail.Baby works well for budget-conscious self-hosters, developers running VPS instances, and small businesses that need reliable outbound email without paying premium prices.

The December 2025 SPF update resolved the biggest security concern. The May 2024 move to in-house infrastructure improved reliability. The REST API and WordPress plugin added integration options that didn’t exist in 2023.

Where it falls short: the 6,000/hour hard cap with no queuing, the cluttered Interserver dashboard, and occasional spam false positives. If you need enterprise-grade deliverability guarantees or a sleek management interface, pay more for Mailgun or SendGrid.

For most self-hosted use cases, like sending transactional email from your applications, monitoring alerts from your VPS, or running email for a small WordPress site, Mail.Baby does the job at a fraction of the cost.

Frequently asked questions