# Email hosting vs email sending service: do you need both?

> Email hosting gives people mailboxes, a sending service delivers your app's mail. Learn the difference, which one you need, and when you need both.

Published 2026-11-20. Source: https://mailions.com/blog/email-hosting-vs-email-sending-service

"I need email for my business" can mean two quite different things. One is a place where people read and answer messages. The other is a way for your website to send messages automatically. Providers sell them under confusingly similar names, and buying the wrong one is a common, annoying mistake.

## Email hosting: mailboxes for people

Email hosting gives you mailboxes on your domain. Each mailbox has a password and storage. People sign in through a browser or an email app, and read, reply, search and organise.

What you get:

- Addresses such as `maria@yourcompany.com`
- IMAP to read and SMTP to send, so any email app works
- Webmail in the browser
- Aliases and forwarding
- Storage, folders, spam handling

The person is the user. The volume is low, usually dozens of messages a day.

## An email sending service: delivery for software

A sending service takes messages from your application and delivers them. There's no inbox to read. Your code calls an API or connects over SMTP, and the service signs, sends and tracks the message.

What you get:

- An API key and an endpoint
- Authentication of your sending domain
- Handling of bounces and retries
- Rate limits and delivery status
- Logs you can look up

The software is the user. The volume can be thousands of messages, triggered by events: sign-ups, purchases, alerts.

## Side by side

| | Email hosting | Sending service |
| --- | --- | --- |
| Main user | A person | Your application |
| Reads incoming mail | Yes | Usually no |
| Typical address | `maria@` | `noreply@` |
| Interface | Webmail and email apps | API or SMTP |
| Volume | Low | Low to very high |
| Examples of mail | Replies, quotes, conversations | Codes, receipts, password resets |

## Which one do you need?

Answer three questions.

1. **Do people on your team send and receive email at your domain?** You need hosting.
2. **Does your website or app send email on its own?** You need a sending service.
3. **Do you want replies to your automated emails to reach a person?** Set `reply_to` to a hosted mailbox, such as `support@`.

Most businesses end up with both. A shop has staff mailboxes for customer conversations, and its website needs to send order confirmations. A SaaS has a founder's inbox and a signup flow that sends codes.

## Why people mix them up

A mailbox can send mail, and SMTP is how it does so. So it's tempting to use a staff mailbox as your application's sender: put `maria@yourcompany.com` and her password in the website's settings. It works at first. Then it becomes a problem:

- Her password is now in your app's configuration, and in anyone's hands who can read it.
- A burst of automated mail from a personal mailbox can get the account limited or flagged.
- Her inbox fills up with bounces and out-of-office replies.
- When she leaves, the website stops sending.

A dedicated sender, either a mailbox just for the app or an API key, avoids all four. Using a separate address like `noreply@` also keeps conversation and automation apart.

## Authentication ties them together

Both need your domain to prove its identity. SPF, DKIM and DMARC records tell receivers which servers may send for you. When both services send under one domain, they must be covered by the same records: one SPF record that includes every sender, and DKIM keys for each. Mistakes here are the top reason legitimate mail goes to spam. [What is SPF](/blog/what-is-spf-record) and [what is DMARC](/blog/what-is-dmarc) explain the details.

If the automated mail is heavy, send it from a subdomain so it builds its own reputation. [Transactional vs marketing email](/blog/transactional-vs-marketing-email) covers why.

## What Mailions offers

We provide both on the same authenticated domain. Add a domain once, publish its records, and you can:

- Create mailboxes for people, with webmail, IMAP and SMTP, aliases and forwarding
- Create API keys for your application, with queued retries when the mail server is briefly unavailable

We don't run newsletters or calendars. Access starts with a conversation: [contact us](/contact) and tell us what you want to send and how many mailboxes you need.

## What it looks like in practice

Picture a small online shop. Two staff members have mailboxes and answer customers all day. The shop's website sends an order confirmation to every buyer, using an API key, from `orders@mail.yourshop.com`, with `reply_to` set to `support@yourshop.com`. A buyer who replies reaches a person. Nobody ever logs in to a mailbox to send an order confirmation.

## A simple plan

1. Add your domain and verify the DNS records.
2. Make mailboxes for the people who need them.
3. Make an API key (or a dedicated SMTP mailbox) for each application that sends mail.
4. Send from `noreply@` or a similar address, and set a human `reply_to`.
5. Test with a message to Gmail and read the authentication headers.

For step-by-step help, see [setting up professional email on your own domain](/blog/setup-professional-email-own-domain) and the [API guide](/help/sending-api).

## Frequently asked questions

### What is the difference between email hosting and an email sending service?

Email hosting gives people mailboxes to receive, store and send everyday mail in apps like Outlook. A sending service delivers mail generated by software, such as password resets and receipts, through an API or SMTP relay, with no inbox to read.

### Can I use my email host to send emails from my app?

For low volumes, often yes, over authenticated SMTP. Mailbox plans have sending limits meant for people, though, so a growing app is better served by a sending API or relay built for automated mail, with logs and retries.

### Do I need separate DNS records for hosting and sending?

Both share the domain's DNS. MX points to the host that receives mail, while SPF, DKIM and DMARC must cover every service that sends as the domain: list all senders in one SPF record and publish a DKIM key for each.
